Triple
T7904349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant Dan Taylor |
E183533
|
entity |
| Predicate | feelsDestinedTo |
P24728
|
FINISHED |
| Object | die in battle |
—
|
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: die in battle | Statement: [Lieutenant Dan Taylor, feelsDestinedTo, die in battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feelsDestinedTo Context triple: [Lieutenant Dan Taylor, feelsDestinedTo, die in battle]
-
A.
destinedFor
Indicates that one entity is intended, assigned, or meant to be used for, received by, or directed toward another entity or purpose.
-
B.
eventualFate
chosen
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
C.
feltIn
Indicates that a sensation, emotion, or effect is experienced within a particular location, context, or entity.
-
D.
feels
Indicates that an entity experiences or has a particular emotion, sensation, or internal state in relation to something.
-
E.
determined
Indicates that an entity has firmly decided on a course of action or conclusion, typically after consideration or effort.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a4331cc8190b50301c78767a850 |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:02 p.m.