Triple
T27902777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ira A. Fulton |
E705680
|
entity |
| Predicate | hasNamed |
P87066
|
FINISHED |
| Object | Ira A. Fulton Schools of Engineering |
—
|
NE NERFINISHED |
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: Ira A. Fulton Schools of Engineering | Statement: [Ira A. Fulton, hasNamed, Ira A. Fulton Schools of Engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamed Context triple: [Ira A. Fulton, hasNamed, Ira A. Fulton Schools of Engineering]
-
A.
hasNaming
chosen
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
B.
hasNamedForRole
Indicates that an entity has been given a specific name or label that corresponds to a particular role it plays.
-
C.
hasGivenNameWith
Indicates that an entity is associated with a specific given (first) name.
-
D.
hasCollectionNamedAfter
Indicates that an entity has a collection (e.g., of works, items, or artifacts) that is named in honor of or after another entity.
-
E.
isNamedAccordingTo
Indicates that one entity receives its name based on, or in accordance with, another entity, rule, or naming convention.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 6:43 p.m.