Triple
T20496566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagobah |
E502888
|
entity |
| Predicate | reasonForYodaExile |
P15406
|
FINISHED |
| Object | remoteness and obscurity |
—
|
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: remoteness and obscurity | Statement: [Dagobah, reasonForYodaExile, remoteness and obscurity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForYodaExile Context triple: [Dagobah, reasonForYodaExile, remoteness and obscurity]
-
A.
causeOfExile
chosen
Indicates the reason or circumstance that led to an entity’s exile.
-
B.
diedInEmpire
Indicates that an entity died while within the territorial or political boundaries of a specified empire.
-
C.
goalOfRebelSide
Indicates that the specified goal is pursued or held by the rebel side in a conflict or opposition scenario.
-
D.
wasExiled
Indicates that an entity was forcibly sent away from their home or country, typically as a punishment or due to political or social pressures.
-
E.
commandedByRebels
Indicates that the authority or control over an entity is exercised by rebel forces or insurgent groups.
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cbdeb9c819090a30a7961146c93 |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.