Triple
T6703171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Maine (ACR-1) |
E152931
|
entity |
| Predicate | removedFromNavyListDate |
P10294
|
FINISHED |
| Object | 1910-03-16 |
—
|
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: 1910-03-16 | Statement: [USS Maine (ACR-1), removedFromNavyListDate, 1910-03-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedFromNavyListDate Context triple: [USS Maine (ACR-1), removedFromNavyListDate, 1910-03-16]
-
A.
strickenFromNavalRegister
chosen
Indicates that a vessel has been officially removed from a navy’s active register, ending its status as a commissioned naval ship.
-
B.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
C.
musteredOutAt
Indicates that an individual was formally discharged or released from service at a specific place or time.
-
D.
disbandedAt
Indicates the time or date at which an organized group, body, or entity formally ceased to exist or operate.
-
E.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
- 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_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. |
Created at: March 27, 2026, 2:06 p.m.