Triple
T4413439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvian lats |
E94905
|
entity |
| Predicate | monetaryUnionJoinDate |
P55509
|
FINISHED |
| Object | 2014-01-01 |
—
|
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: 2014-01-01 | Statement: [Latvian lats, monetaryUnionJoinDate, 2014-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetaryUnionJoinDate Context triple: [Latvian lats, monetaryUnionJoinDate, 2014-01-01]
-
A.
monetaryUnionReplacedBy
Indicates that one monetary union has been succeeded or superseded by another monetary union.
-
B.
monetaryUnionEvent
Indicates an event in which two or more entities establish, join, modify, or dissolve a shared monetary system or common currency arrangement.
-
C.
monetaryUnionContext
Indicates a context in which entities are related through participation in, or relevance to, a shared monetary union or common currency area.
-
D.
monetaryUnionPartner
Indicates that two entities are members of the same monetary union, sharing a common currency or coordinated monetary policy.
-
E.
monetaryUnionGoal
Indicates that one entity has the objective or aim of forming or participating in a monetary union with another entity.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e7b30c819082ee781dd202dcc4 |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff7018c81908ad8597e525c042b |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:29 p.m.