Triple
T616044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiral Graf Spee |
E14405
|
entity |
| Predicate | enteredMontevideoDate |
P17167
|
FINISHED |
| Object | 1939-12-14 |
—
|
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: 1939-12-14 | Statement: [Admiral Graf Spee, enteredMontevideoDate, 1939-12-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredMontevideoDate Context triple: [Admiral Graf Spee, enteredMontevideoDate, 1939-12-14]
-
A.
placeOfArrival
Indicates the location at which an entity or person arrives at the end of a journey, movement, or transfer.
-
B.
admittedToUnionOn
Indicates that an entity (typically a state or region) was formally accepted and incorporated into a union or federation on a specific date.
-
C.
immigratedTo
Indicates that an entity moved from its country of origin to live permanently in another specified country or region.
-
D.
settledInYear
Indicates the specific calendar year in which an entity became established, inhabited, or formally settled in a particular place or status.
-
E.
hasBorderCrossing
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e0b438881909ad515adf7a4eb79 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49def31ec81909dc53e70f4a36eda |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.