Triple
T35312904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (NCC-1701-C) |
E1019823
|
entity |
| Predicate | sacrificeOutcome |
P129085
|
FINISHED |
| Object | improved Federation–Klingon relations |
—
|
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: improved Federation–Klingon relations | Statement: [USS Enterprise (NCC-1701-C), sacrificeOutcome, improved Federation–Klingon relations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacrificeOutcome Context triple: [USS Enterprise (NCC-1701-C), sacrificeOutcome, improved Federation–Klingon relations]
-
A.
resultOfSacrifice
chosen
Indicates that something exists or occurs as the outcome or consequence of a sacrificial act.
-
B.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
C.
sacrificeType
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
D.
sacrificedTo
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, another entity.
-
E.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7905842808190a4fc9917f0f4b60d |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.