Triple
T36206886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Oceanic |
E1047421
|
entity |
| Predicate | enteredMilitaryService |
P129029
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [RMS Oceanic, enteredMilitaryService, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredMilitaryService Context triple: [RMS Oceanic, enteredMilitaryService, 1914]
-
A.
enteredUSArmyService
Indicates that an individual began active service in the United States Army at a specific point in time.
-
B.
enteredNATOService
Indicates that an entity (typically a military asset or unit) began active operational service under NATO command or within NATO forces.
-
C.
hadMilitaryServiceFrom
chosen
Indicates that an entity performed or was engaged in military service starting from a specified point in time.
-
D.
involvesMilitaryService
Indicates that the relationship or situation includes participation in, obligation to, or association with formal military service.
-
E.
musteredIntoService
Indicates that an entity has been formally enrolled or assembled into active duty or official service under an authority.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.