Triple
T26346793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECW One Night Stand 2006 main event |
E662796
|
entity |
| Predicate | foreignObjectUsed |
P126429
|
FINISHED |
| Object | steel chair |
—
|
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: steel chair | Statement: [ECW One Night Stand 2006 main event, foreignObjectUsed, steel chair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foreignObjectUsed Context triple: [ECW One Night Stand 2006 main event, foreignObjectUsed, steel chair]
-
A.
objectUsed
chosen
Indicates that one entity is used as a tool, instrument, or resource in performing an action involving another entity.
-
B.
usesFoundObject
Indicates that an entity makes use of an object that it has previously found or discovered.
-
C.
usesReferenceObjects
Indicates that an entity performs an action or makes a determination by relying on one or more other entities as reference points or benchmarks.
-
D.
usedOutside
Indicates that something is utilized or applied in a context, location, or situation external to its primary or original setting.
-
E.
notableObject
Indicates that an entity is especially significant, famous, or noteworthy as an object in a given context or domain.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 26, 2026, 10:42 p.m.