Triple
T35985418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLC: Tables, Ladders & Chairs |
E1040694
|
entity |
| Predicate | usesRingObjectsAsWeapons |
P706
|
FINISHED |
| Object | tables |
—
|
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: tables | Statement: [TLC: Tables, Ladders & Chairs, usesRingObjectsAsWeapons, tables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRingObjectsAsWeapons Context triple: [TLC: Tables, Ladders & Chairs, usesRingObjectsAsWeapons, tables]
-
A.
usedWeapon
chosen
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
B.
wieldedFrom
Indicates that an entity uses or brandishes another entity as a weapon or tool originating from a particular source or location.
-
C.
symbolicWeapon
Indicates a relationship where something functions as a symbolic or emblematic weapon for an entity, representing power, threat, or conflict rather than serving as a literal physical armament.
-
D.
oftenEquippedWith
Indicates that one type of entity is frequently or typically outfitted, furnished, or supplied with another entity.
-
E.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:07 p.m.