Triple
T26346567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Hardcore Championship |
E662789
|
entity |
| Predicate | defenseLocationScope |
P13939
|
FINISHED |
| Object | any time any place |
—
|
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: any time any place | Statement: [WWE Hardcore Championship, defenseLocationScope, any time any place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenseLocationScope Context triple: [WWE Hardcore Championship, defenseLocationScope, any time any place]
-
A.
defenseArea
Indicates a spatial region or zone that is designated for defensive protection or military/security defense activities.
-
B.
locationScope
chosen
Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
-
C.
securityLocation
Indicates the place or area where security-related activities, measures, or responsibilities are situated or applied.
-
D.
defenseStatus
Indicates the current state or condition of an entity’s defensive posture or protective readiness in a given context.
-
E.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 26, 2026, 10:42 p.m.