Triple
T2987803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoth |
E80668
|
entity |
| Predicate | notableCharacterActivity |
P36130
|
FINISHED |
| Object | Luke Skywalker patrols on tauntaun |
—
|
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: Luke Skywalker patrols on tauntaun | Statement: [Hoth, notableCharacterActivity, Luke Skywalker patrols on tauntaun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterActivity Context triple: [Hoth, notableCharacterActivity, Luke Skywalker patrols on tauntaun]
-
A.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
B.
notableDeed
chosen
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
-
C.
notableAppearance
Indicates that an entity is prominently featured or makes a significant appearance in another work, event, or context.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c9cdd081908fa8094a3ac1f8d3 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.