Triple
T29384995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDP |
E745226
|
entity |
| Predicate | geopoliticalLevel |
P2887
|
FINISHED |
| Object | European |
—
|
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 | Statement: [CDP, geopoliticalLevel, European]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geopoliticalLevel Context triple: [CDP, geopoliticalLevel, European]
-
A.
geopoliticalScope
chosen
Indicates the geographic or political area within which an entity’s authority, relevance, or effect is defined or applies.
-
B.
geopoliticalConcept
Indicates a conceptual or abstract geopolitical relationship, such as a political, territorial, or strategic notion connecting entities within a geopolitical context.
-
C.
geopoliticalSignificance
Indicates the importance or influence that a place, event, or relationship holds within regional or global political and strategic power dynamics.
-
D.
geopoliticalRegion
Indicates a relationship where an entity is a defined political or administrative geographic area, such as a country, state, province, or similar region.
-
E.
geopoliticalResult
Indicates the outcome or consequence of a geopolitical event, action, or interaction between political 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d0c45c8190ac5b67a0e89e8aae |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:38 p.m.