Triple
T12119214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Constitution Revision Commission |
E288646
|
entity |
| Predicate | firstConvenedInYear |
P13757
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [Florida Constitution Revision Commission, firstConvenedInYear, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstConvenedInYear Context triple: [Florida Constitution Revision Commission, firstConvenedInYear, 1977]
-
A.
firstParliamentStart
Indicates the date or point in time when an entity’s first parliamentary term or session began.
-
B.
yearOfCouncilReferenced
Indicates that one entity specifies or cites the calendar year in which a particular council took place.
-
C.
firstCongressDate
chosen
Indicates the calendar date on which the first congress or formal assembly associated with an entity took place.
-
D.
firstElectionYear
Indicates the calendar year in which an entity (such as a person, office, or political body) first participated in or was subject to an election.
-
E.
firstMeetingYear
Indicates the calendar year in which two entities first met or had their initial encounter.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.