Triple
T776080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Jeremiah O’Brien |
E16388
|
entity |
| Predicate | yearsInReserve |
P19648
|
FINISHED |
| Object | about 33 years |
—
|
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: about 33 years | Statement: [SS Jeremiah O’Brien, yearsInReserve, about 33 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearsInReserve Context triple: [SS Jeremiah O’Brien, yearsInReserve, about 33 years]
-
A.
relocationYear
Indicates the year in which an entity was moved or transferred from one location to another.
-
B.
activeYearsInCareer
Indicates the span of time during which an entity was actively engaged in a particular career or professional field.
-
C.
retiredNumber
Indicates that an entity (typically a team or organization) has formally withdrawn a specific number from future use, usually to honor a particular individual or achievement associated with that number.
-
D.
reserves
Indicates that an entity has arranged in advance to hold or secure something for future use or access.
-
E.
leagueEntryYear
Indicates the year in which an entity first entered or joined a particular league.
- F. None of above. chosen
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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a50a443481909ae3662764ee69a4 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a74c81bc81909f4ac9c1677b09c2 |
completed | March 1, 2026, 8:53 p.m. |
Created at: March 1, 2026, 7:37 p.m.