Triple
T14286519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Face of Boe |
E354188
|
entity |
| Predicate | sacrificesSelfTo |
P113058
|
FINISHED |
| Object | save the motorists in "Gridlock" |
—
|
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: save the motorists in "Gridlock" | Statement: [The Face of Boe, sacrificesSelfTo, save the motorists in "Gridlock"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacrificesSelfTo Context triple: [The Face of Boe, sacrificesSelfTo, save the motorists in "Gridlock"]
-
A.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
B.
sacrificedLifeToSaveOthers
chosen
Indicates that an entity willingly gave up their own life in order to protect or rescue other entities.
-
C.
sacrificedTo
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, another entity.
-
D.
sacrificeType
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
E.
sacrificedBefore
Indicates that one entity was sacrificed earlier in time than another entity.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697ef40c8190bea37724b28c2e99 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.