Triple
T33119384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BFG 9000 |
E847550
|
entity |
| Predicate | weaponSlot |
P63771
|
FINISHED |
| Object | top-tier weapon |
—
|
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: top-tier weapon | Statement: [BFG 9000, weaponSlot, top-tier weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponSlot Context triple: [BFG 9000, weaponSlot, top-tier weapon]
-
A.
weaponMount
Indicates that one entity serves as a mounting point or support structure for attaching or holding a weapon on another entity.
-
B.
loadoutSlot
chosen
Indicates the specific equipment or item slot in which a particular piece of gear or object is placed within a loadout configuration.
-
C.
weaponControl
Indicates that one entity has authority over, access to, or the ability to direct the use of a weapon associated with another entity.
-
D.
positionOnWeapons
Indicates a stance, policy, or viewpoint that an entity holds regarding weapons or weapon-related issues.
-
E.
enablesWeapon
Indicates that one entity provides the capability for another entity to use, activate, or access a weapon.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:27 a.m.