Triple
T6703167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Maine (ACR-1) |
E152931
|
entity |
| Predicate | arrivalInHavanaDate |
P72524
|
FINISHED |
| Object | 1898-01-25 |
—
|
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: 1898-01-25 | Statement: [USS Maine (ACR-1), arrivalInHavanaDate, 1898-01-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrivalInHavanaDate Context triple: [USS Maine (ACR-1), arrivalInHavanaDate, 1898-01-25]
-
A.
arrivalDatePlanned
Indicates the date on which an arrival is scheduled or expected to occur according to a plan.
-
B.
arrivalDateInBrazil
Indicates the date on which an entity arrives or is scheduled to arrive in Brazil.
-
C.
dateOfDisembarkation
Indicates the specific date on which an individual or entity got off or was released from a vehicle, vessel, or mode of transport.
-
D.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
E.
dateOfPacificArrival
Indicates the date on which an entity arrived at a location on or in the Pacific region.
- 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_69c68807adbc8190b8632df42b39eda0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:06 p.m.