Triple
T35907646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSCE Summit |
E1038514
|
entity |
| Predicate | coversStatesFrom |
P193333
|
FINISHED |
| Object | Europe |
—
|
NE NERFINISHED |
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: Europe | Statement: [OSCE Summit, coversStatesFrom, Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversStatesFrom Context triple: [OSCE Summit, coversStatesFrom, Europe]
-
A.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
B.
coversStateInCombination
Indicates that an entity, together with one or more other entities, collectively provides coverage for a given state or jurisdiction.
-
C.
coversTo
Indicates that one entity extends its coverage or protective scope to include another entity.
-
D.
divisionCoversStates
Indicates that a particular division has jurisdiction over, includes, or is responsible for the specified states.
-
E.
coversAllCountiesIn
Indicates that one entity provides complete coverage or service across all counties within the specified region.
- F. None of above. chosen
Provenance (4 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: May 3, 2026, 4:07 p.m.