Triple
T35842827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROH World Tag Team Championship |
E1036131
|
entity |
| Predicate | canBeVacatedFor |
P28480
|
FINISHED |
| Object | injury |
—
|
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: injury | Statement: [ROH World Tag Team Championship, canBeVacatedFor, injury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeVacatedFor Context triple: [ROH World Tag Team Championship, canBeVacatedFor, injury]
-
A.
canBeVacated
chosen
Indicates that a position, status, or decision is capable of being annulled, set aside, or rendered void.
-
B.
canBeVacant
Indicates that an entity (such as a position, property, or role) is capable of being unoccupied or without an assigned holder.
-
C.
canBeVacantWhen
Indicates the conditions or circumstances under which something is allowed or able to remain unoccupied or empty.
-
D.
vacatedWhen
Indicates the time or date at which something (such as a position, office, or place) was given up, left, or no longer occupied.
-
E.
seatVacatedBy
Indicates that a particular seat has been freed or relinquished as a result of an action performed by a specific 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: May 3, 2026, 4:06 p.m.