Triple
T29322390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Pit of Carkoon |
E743546
|
entity |
| Predicate | notableWeaponUsedNearby |
P204178
|
FINISHED |
| Object | Luke Skywalker's lightsaber |
—
|
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's lightsaber | Statement: [Great Pit of Carkoon, notableWeaponUsedNearby, Luke Skywalker's lightsaber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWeaponUsedNearby Context triple: [Great Pit of Carkoon, notableWeaponUsedNearby, Luke Skywalker's lightsaber]
-
A.
weaponUsedIn
Indicates that a particular weapon is employed or involved in carrying out a specific event or action.
-
B.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
C.
weaponUsedOn
Indicates that a particular weapon was employed or applied against a specific target or entity.
-
D.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
E.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
- F. None of above. chosen
Provenance (4 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a03446ec72881909c5ff25a48baadb3 |
completed | May 12, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_6a03439b393c819084aa9b7ed0d5b6b0 |
completed | May 12, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_6a03446d9d988190981f245d74c3444b |
completed | May 12, 2026, 3:17 p.m. |
Created at: April 28, 2026, 1:24 p.m.