Triple
T368980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | March Constitution of 1921 |
E8225
|
entity |
| Predicate | effectiveUntil |
P140
|
FINISHED |
| Object | 1935-04-23 |
—
|
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: 1935-04-23 | Statement: [March Constitution of 1921, effectiveUntil, 1935-04-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveUntil Context triple: [March Constitution of 1921, effectiveUntil, 1935-04-23]
-
A.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
B.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
C.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
D.
durationUntil
Indicates the length of time remaining from a given starting point until a specified future event or state occurs.
-
E.
expirationPolicy
Indicates the rules or conditions under which something becomes invalid, unusable, or no longer in effect after a certain time or event.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebfdb0608190b1794a871d0d237a |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.