Triple
T2735712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Friso of Orange-Nassau |
E60624
|
entity |
| Predicate | skiingAccidentDate |
P36827
|
FINISHED |
| Object | 2012-02-17 |
—
|
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: 2012-02-17 | Statement: [Prince Friso of Orange-Nassau, skiingAccidentDate, 2012-02-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skiingAccidentDate Context triple: [Prince Friso of Orange-Nassau, skiingAccidentDate, 2012-02-17]
-
A.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
B.
injuryDate
chosen
Indicates the date on which an injury occurred or was sustained.
-
C.
missionAccidentDate
Indicates the date on which an accident occurred during or in relation to a mission.
-
D.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
E.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb1022488190af84e536946b2e37 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.