Triple
T26298235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montenegro |
E661476
|
entity |
| Predicate | usesEuroFormallyInEU |
P11136
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Montenegro, usesEuroFormallyInEU, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEuroFormallyInEU Context triple: [Montenegro, usesEuroFormallyInEU, false]
-
A.
containsEuroSign
Indicates that the referenced text or string includes at least one euro currency symbol (€).
-
B.
adoptedEuro
chosen
Indicates that a country or entity has officially adopted the euro as its legal currency.
-
C.
usesEuropeanUnionDSTRules
Indicates that the action or process is governed by, or conforms to, the European Union’s Digital Services Act (DSA) rules and requirements.
-
D.
notAllEUMembersUseEuro
Indicates that the set of all EU member states is not identical to the set of countries using the euro, i.e., at least one EU member does not use the euro as its official currency.
-
E.
isProEuropean
Indicates support for European integration, institutions, or policies, or a generally favorable stance toward the European Union.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eafb8a0819090f8db1feca43f64 |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:13 p.m.