Triple
T36004647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pilot |
E1041229
|
entity |
| Predicate | primaryReadership |
P10804
|
FINISHED |
| Object | Irish Americans |
E1437
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Irish Americans | Statement: [The Pilot, primaryReadership, Irish Americans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryReadership Context triple: [The Pilot, primaryReadership, Irish Americans]
-
A.
readership
Indicates the relationship in which one party reads, follows, or is the audience for the written or published work of another.
-
B.
secondaryAudience
Indicates that an entity is a secondary or additional intended audience or target group for another entity (such as a work, message, or product), beyond the primary audience.
-
C.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
D.
primaryUsersOf
Indicates that the subject is the main or most frequent user(s) of the object.
-
E.
primaryMedium
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38bff3d3688190b5dca82c12d426be |
completed | June 22, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.