Triple
T35203680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Raw Women’s Championship |
E1016476
|
entity |
| Predicate | lineageStart |
P108534
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [WWE Raw Women’s Championship, lineageStart, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineageStart Context triple: [WWE Raw Women’s Championship, lineageStart, 2016]
-
A.
lineageSystem
Indicates a hierarchical ancestry or descent relationship that traces how entities are derived from or originate through one another within a system.
-
B.
titleLineageStart
chosen
Indicates the point in time or event at which a particular title or rank first begins within a lineage or succession.
-
C.
lineagePosition
Indicates the relative placement or rank of an entity within a lineage or ancestral chain.
-
D.
hasLineageStart
Indicates that an entity originates from, or traces its lineage back to, a specified starting ancestor or source in a lineage chain.
-
E.
lineageClaim
Indicates a claim or assertion that one entity is descended from, or belongs to the ancestral line of, 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.