Triple
T473352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Constitution |
E9006
|
entity |
| Predicate | currentVersionEffectiveFrom |
P4988
|
FINISHED |
| Object | 1876-04-18 |
—
|
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: 1876-04-18 | Statement: [Texas Constitution, currentVersionEffectiveFrom, 1876-04-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentVersionEffectiveFrom Context triple: [Texas Constitution, currentVersionEffectiveFrom, 1876-04-18]
-
A.
currentISOCodeEffectiveFrom
Indicates the date and time from which the current ISO code for an entity becomes valid or officially in effect.
-
B.
currentDesignInForceSince
chosen
Indicates the date or point in time from which the current design has been officially in effect or valid.
-
C.
preliminaryVersionDate
Indicates the date on which an initial or draft version of something was created, issued, or became available.
-
D.
currentVersionDefinedIn
Indicates that the current or active version of an entity is specified or established within a particular source, document, or context.
-
E.
doesNotApplyRetroactivelyTo
Indicates that a rule, law, or condition does not affect events, actions, or situations that occurred before it came into effect.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0208c788190a96cdabcf593fda7 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.