Triple
T22495629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John S. McCain III Terminal |
E556130
|
entity |
| Predicate | isNamedForRole |
P53948
|
FINISHED |
| Object | United States Senator |
—
|
LITERAL 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: United States Senator | Statement: [John S. McCain III Terminal, isNamedForRole, United States Senator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedForRole Context triple: [John S. McCain III Terminal, isNamedForRole, United States Senator]
-
A.
isNamedForEponymRole
chosen
Indicates that one entity bears a name derived from another entity that serves as its eponym or namesake.
-
B.
hasNamesakeRoleFor
Indicates that one entity holds a role or position that is named after, or serves as a namesake for, another entity.
-
C.
isNamedFor
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
D.
isNamedEntity
Indicates that the subject is recognized as a named entity, such as a specific person, organization, location, or other proper noun.
-
E.
namedIn
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
- F. None of above.
Provenance (3 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb19bac81909bbc2f131186aeea |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.