Triple
T8609645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Uruguay |
E203884
|
entity |
| Predicate | currentVersionInForceSince |
P17807
|
FINISHED |
| Object | 1967 |
—
|
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: 1967 | Statement: [Constitution of Uruguay, currentVersionInForceSince, 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentVersionInForceSince Context triple: [Constitution of Uruguay, currentVersionInForceSince, 1967]
-
A.
currentVersionEffectiveDate
Indicates the date from which the current version of an item, record, or agreement becomes valid and in effect.
-
B.
officialVersionSince
Indicates the point in time from which a particular version of something is recognized or treated as the official version.
-
C.
currentDesignInForceSince
Indicates the date or point in time from which the current design has been officially in effect or valid.
-
D.
inForceSince
chosen
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
-
E.
currentVersionAdopted
Indicates that a specified version is the one presently in use or officially adopted by the relevant entity or system.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ed77588190a872d22d9d1f7429 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.