Triple
T17752234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTL |
E443139
|
entity |
| Predicate | usedBeforeEuroAdoption |
P7341
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LTL, usedBeforeEuroAdoption, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBeforeEuroAdoption Context triple: [LTL, usedBeforeEuroAdoption, true]
-
A.
adoptedEuro
Indicates that a country or entity has officially adopted the euro as its legal currency.
-
B.
peggedToEuroSince
Indicates that the value of one currency or financial instrument has been fixed or tightly linked to the euro starting from a specific point in time.
-
C.
replacedByInEurope
Indicates that one entity has been superseded or substituted by another specifically within the geographic context of Europe.
-
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.
usedBefore
chosen
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841b3ccc8190b3241b3e0fa4b2e8 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.