Triple
T26346571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Hardcore Championship |
E662789
|
entity |
| Predicate | titleLineageStatus |
P178763
|
FINISHED |
| Object | inactive |
—
|
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: inactive | Statement: [WWE Hardcore Championship, titleLineageStatus, inactive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleLineageStatus Context triple: [WWE Hardcore Championship, titleLineageStatus, inactive]
-
A.
titleHolderLineage
Indicates the succession relationship showing which entity inherited or held a title from which predecessor in a lineage.
-
B.
titleLineageStart
Indicates the point in time or event at which a particular title or rank first begins within a lineage or succession.
-
C.
hasLineageStatus
Indicates the lineage or ancestry classification assigned to an entity, such as whether and how it descends from or is derived from another.
-
D.
titleStatus
Indicates the current legal or administrative state of a title (such as ownership, validity, or processing stage) in relation to an entity or record.
-
E.
titleLineageMaintainedBy
Indicates that the continuity or inheritance of a title is preserved or upheld by a specified entity.
- F. None of above. chosen
Provenance (4 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_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 26, 2026, 10:42 p.m.