Triple
T29138618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Chief |
E738569
|
entity |
| Predicate | closeQuartersWeapon |
P7745
|
FINISHED |
| Object | Energy sword (captured from Covenant) |
—
|
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: Energy sword (captured from Covenant) | Statement: [Master Chief, closeQuartersWeapon, Energy sword (captured from Covenant)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closeQuartersWeapon Context triple: [Master Chief, closeQuartersWeapon, Energy sword (captured from Covenant)]
-
A.
limitedWeaponType
Indicates that the use or availability of a weapon is restricted to a specific type or set of types.
-
B.
weaponDepicted
Indicates that a weapon is visually represented or shown in association with an entity.
-
C.
lightArmament
Indicates that an entity is equipped with or characterized by relatively minimal or lightweight weaponry compared to standard or heavy armament.
-
D.
weaponUsedIn
Indicates that a particular weapon is employed or involved in carrying out a specific event or action.
-
E.
typicalWeapon
chosen
Indicates that the object is a weapon commonly or characteristically used by the subject.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 11:35 a.m.