Triple
T34926094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Riker |
E1007287
|
entity |
| Predicate | settingOfOriginEvent |
P111438
|
FINISHED |
| Object | Nervala IV station |
—
|
NE NERFINISHED |
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: Nervala IV station | Statement: [Thomas Riker, settingOfOriginEvent, Nervala IV station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfOriginEvent Context triple: [Thomas Riker, settingOfOriginEvent, Nervala IV station]
-
A.
originalLocationEvent
chosen
Indicates that an event occurred at or is associated with the place where an entity was originally located or originated.
-
B.
causeOfOrigin
Indicates that one entity is the source or initiating cause from which another entity originates or comes into existence.
-
C.
physicalOrigin
Indicates that one entity is the place or source from which another entity physically originates or comes into existence.
-
D.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
E.
signalOrigin
Indicates that one entity is the source or starting point from which a signal is generated or transmitted to others.
- 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4 p.m.