Triple
T32559481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderdome arena |
E832182
|
entity |
| Predicate | weaponPlacement |
P57777
|
FINISHED |
| Object | mounted on cage walls |
—
|
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: mounted on cage walls | Statement: [Thunderdome arena, weaponPlacement, mounted on cage walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponPlacement Context triple: [Thunderdome arena, weaponPlacement, mounted on cage walls]
-
A.
weaponMount
chosen
Indicates that one entity serves as a mounting point or support structure for attaching or holding a weapon on another entity.
-
B.
positionOnWeapons
Indicates a stance, policy, or viewpoint that an entity holds regarding weapons or weapon-related issues.
-
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.
weaponControlMethod
Indicates how a weapon is operated, activated, or controlled in order to perform its intended function.
-
E.
weaponDepicted
Indicates that a weapon is visually represented or shown in association with an entity.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:03 a.m.