Triple
T2659881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article V of the Florida Constitution |
E54700
|
entity |
| Predicate | wasAdoptedIn |
P3076
|
FINISHED |
| Object | 1968 Florida Constitution revision |
—
|
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: 1968 Florida Constitution revision | Statement: [Article V of the Florida Constitution, wasAdoptedIn, 1968 Florida Constitution revision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAdoptedIn Context triple: [Article V of the Florida Constitution, wasAdoptedIn, 1968 Florida Constitution revision]
-
A.
adoptedAt
chosen
Indicates the time or date at which an adoption event took place.
-
B.
adoptedInCity
Indicates that an adoption event took place within a specific city.
-
C.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
-
D.
readoptedOn
Indicates the date or time at which something that was previously adopted is formally adopted again.
-
E.
adoptedThrough
Indicates that an adoption relationship was established or carried out by means of a specified process, channel, or intermediary.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94f3b1881909bd36cfe61c254a5 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.