Triple
T37513780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travincal |
E932578
|
entity |
| Predicate | objectiveInvolves |
P120603
|
FINISHED |
| Object | defeating the High Council |
—
|
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: defeating the High Council | Statement: [Travincal, objectiveInvolves, defeating the High Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveInvolves Context triple: [Travincal, objectiveInvolves, defeating the High Council]
-
A.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
B.
objectiveIncludes
Indicates that a broader objective encompasses or contains a specific sub-objective, component, or element as part of its scope.
-
C.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
goalAssociatedWith
chosen
Indicates that a goal is connected or linked to another entity, such as an activity, plan, or outcome, in a way that reflects relevance or influence.
-
E.
goalImposedOn
Indicates that a specific goal or objective is assigned or mandated by one entity for another entity to pursue or achieve.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.