Triple
T14407256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 205 Live |
E357230
|
entity |
| Predicate | usesRingType |
P66253
|
FINISHED |
| Object | professional wrestling ring |
—
|
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: professional wrestling ring | Statement: [205 Live, usesRingType, professional wrestling ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRingType Context triple: [205 Live, usesRingType, professional wrestling ring]
-
A.
usesRingStyle
Indicates that one entity performs or operates using a particular ring-based style, method, or format.
-
B.
hasRing
Indicates that one entity possesses, wears, or is characterized by the presence of a ring.
-
C.
ringType
chosen
Indicates the specific kind or category of ring associated with an entity or relationship.
-
D.
associatedWithRing
Indicates that an entity has a connection or relationship with a specific ring, such as ownership, membership, or involvement.
-
E.
hasRingPersonaType
Indicates that an entity’s type or role is defined specifically in the context of its ring-related persona or identity.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90c7a068819081b4b516983a1412 |
completed | April 14, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69de2aa1b57881909a033eac8545c417 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.