Triple
T13242714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raw Women’s Championship |
E315319
|
entity |
| Predicate | renamedContext |
P30638
|
FINISHED |
| Object | brand split era |
—
|
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: brand split era | Statement: [Raw Women’s Championship, renamedContext, brand split era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamedContext Context triple: [Raw Women’s Championship, renamedContext, brand split era]
-
A.
contextOfRenaming
chosen
Indicates the situational or historical context in which an entity’s name was or is being changed.
-
B.
relocationContext
Indicates the circumstances, reasons, and situational details surrounding an entity’s move or transfer from one place or position to another.
-
C.
originContext
Indicates the situational or environmental circumstances from which an entity, event, or piece of information originates.
-
D.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
E.
renamedEntity
Indicates that one entity has been given a new name, linking the original entity to its updated or replacement name.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d59e84c8190a9e547d0fe26a5f9 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.