Triple
T2497576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Small Constitution of 1947 |
E52187
|
entity |
| Predicate | effectiveUntilYear |
P214
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [Small Constitution of 1947, effectiveUntilYear, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveUntilYear Context triple: [Small Constitution of 1947, effectiveUntilYear, 1952]
-
A.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
B.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
C.
activeYearsEndTime
Indicates the point in time when an entity’s period of activity or operation comes to an end.
-
D.
endYear
chosen
Indicates the year in which an event, state, or relationship comes to an end.
-
E.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1ad2f8c81908853e97d75081e84 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.