Triple
T33310377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Celtic |
E852859
|
entity |
| Predicate | returnedToCivilianService |
P19195
|
FINISHED |
| Object | 1919 |
—
|
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: 1919 | Statement: [SS Celtic, returnedToCivilianService, 1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToCivilianService Context triple: [SS Celtic, returnedToCivilianService, 1919]
-
A.
retiredFromUSMilitary
Indicates that an individual previously served in the United States military and has formally ended their military career or service.
-
B.
retiredFromUSMCFrontlineService
Indicates that an individual has ended their active frontline duty service in the United States Marine Corps.
-
C.
retiredFromFrontlineService
Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
-
D.
hasMilitaryServiceEnd
chosen
Indicates the date or point in time at which an entity’s period of military service concludes.
-
E.
stanceOnMilitaryService
Indicates an entity’s expressed position, attitude, or policy regarding military service.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 1, 2026, 1:33 a.m.