Triple
T34982236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krenim |
E1008844
|
entity |
| Predicate | temporalIncursionPurpose |
P125181
|
FINISHED |
| Object | to improve strategic position of the Imperium |
—
|
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: to improve strategic position of the Imperium | Statement: [Krenim, temporalIncursionPurpose, to improve strategic position of the Imperium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalIncursionPurpose Context triple: [Krenim, temporalIncursionPurpose, to improve strategic position of the Imperium]
-
A.
timeTravelPurpose
chosen
Indicates that an instance of time travel is undertaken with a specific goal, motive, or intended outcome in mind.
-
B.
timeTravelTrigger
Indicates an event, condition, or mechanism that initiates or enables time travel to occur.
-
C.
hasTemporalParadox
Indicates that a situation, event, or sequence of events involves a contradiction or inconsistency in time, such as conflicting timelines or causality loops.
-
D.
usesTimeTravelFor
Indicates a relationship where an entity employs time travel as a means or method to achieve, affect, or interact with another entity or objective.
-
E.
temporal
Indicates a relationship that situates one event, state, or entity in time relative to another (e.g., before, after, or during).
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.