Triple
T25672649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohrid Framework Agreement |
E643718
|
entity |
| Predicate | countryContextPresentDay |
P140470
|
FINISHED |
| Object | North Macedonia |
—
|
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: North Macedonia | Statement: [Ohrid Framework Agreement, countryContextPresentDay, North Macedonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryContextPresentDay Context triple: [Ohrid Framework Agreement, countryContextPresentDay, North Macedonia]
-
A.
presentDayGeographicalContext
chosen
Indicates the current geographical setting or location in which an entity, event, or relationship exists or is situated.
-
B.
presentDayCityRegion
Indicates that a city is located within or associated with a particular region in the present day.
-
C.
presentDayCityIs
Indicates that one entity is the current, modern-day city corresponding to or located at the place represented by the other entity.
-
D.
presentDayCityCountry
Indicates that a given city is located in a specified country in the present day.
-
E.
administrativeDivisionToday
Indicates that one entity currently functions as an administrative subdivision or jurisdictional unit within the other.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 21, 2026, 7:30 p.m.