Triple
T558935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Europe |
E13404
|
entity |
| Predicate | regionSpecificCoverage |
P5596
|
FINISHED |
| Object | European Union politics |
—
|
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: European Union politics | Statement: [Time Europe, regionSpecificCoverage, European Union politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionSpecificCoverage Context triple: [Time Europe, regionSpecificCoverage, European Union politics]
-
A.
regionSpecificContent
chosen
Indicates that certain content is tailored, restricted, or applicable only to a particular geographic region or set of regions.
-
B.
regionException
Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
-
C.
jurisdictionCovered
Indicates that a particular jurisdiction or legal authority is included within the scope or coverage of another entity, rule, or arrangement.
-
D.
reignCoverage
Indicates the temporal span or extent over which a ruler’s reign or authority is in effect.
-
E.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499df43f08190b514a38d36fc271d |
completed | March 1, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69a494bd78e8819083c519669158f209 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.