Triple
T2024568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus Platform |
E44178
|
entity |
| Predicate | yearOfPredecessor |
P33884
|
FINISHED |
| Object | 1885 |
—
|
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: 1885 | Statement: [Columbus Platform, yearOfPredecessor, 1885]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfPredecessor Context triple: [Columbus Platform, yearOfPredecessor, 1885]
-
A.
cededYear
Indicates the year in which control, ownership, or sovereignty over something was formally transferred from one party to another.
-
B.
historicalEntityPredecessor
Indicates that one historical entity existed or held a role before another, serving as its predecessor in time or sequence.
-
C.
successorAdoptionYear
chosen
Indicates the year in which a successor entity formally adopted or took over from its predecessor.
-
D.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
E.
predecessorInOffice
Indicates that one officeholder directly held a particular position before another officeholder in an official succession.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f2cd5c8190b19da6f6aa2001d6 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.