Triple
T35471386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exo |
E1025216
|
entity |
| Predicate | hasOriginLocationInLore |
P32195
|
FINISHED |
| Object | Europa |
—
|
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: Europa | Statement: [Exo, hasOriginLocationInLore, Europa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginLocationInLore Context triple: [Exo, hasOriginLocationInLore, Europa]
-
A.
hasOriginStoryLocation
chosen
Indicates that an entity’s origin story takes place at or is associated with a specific location.
-
B.
hasSettingOfOrigin
Indicates that something originates from, or was initially set in, a particular setting or environment.
-
C.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
D.
hasCursedLocation
Indicates a relationship where a location is affected by or associated with a curse.
-
E.
hasFictionalLocation
Indicates that an entity is associated with, set in, or takes place within a location that exists only in fiction rather than in the real world.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:04 p.m.