Triple
T5585710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Tulane |
E146749
|
entity |
| Predicate | causeOfRenaming |
P50866
|
FINISHED |
| Object | University of Louisiana renamed as Tulane University |
—
|
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: University of Louisiana renamed as Tulane University | Statement: [Paul Tulane, causeOfRenaming, University of Louisiana renamed as Tulane University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfRenaming Context triple: [Paul Tulane, causeOfRenaming, University of Louisiana renamed as Tulane University]
-
A.
renamedDueTo
chosen
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
B.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
-
C.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
D.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
E.
contextOfRenaming
Indicates the situational or historical context in which an entity’s name was or is being changed.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020871a3c8190991f291295cadfa5 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.