Triple
T31493568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Treaty |
E803476
|
entity |
| Predicate | ratifiedBySpainOn |
P1036
|
FINISHED |
| Object | 1820-10-24 |
—
|
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: 1820-10-24 | Statement: [Florida Treaty, ratifiedBySpainOn, 1820-10-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ratifiedBySpainOn Context triple: [Florida Treaty, ratifiedBySpainOn, 1820-10-24]
-
A.
ratifiedByUnitedStatesOn
Indicates that an agreement, treaty, or document was formally approved and ratified by the United States on a specific date.
-
B.
establishedAsSpanishTerritory
Indicates that an entity was formally designated or recognized as territory under Spanish control or sovereignty.
-
C.
ratifiedOn
chosen
Indicates the date or point in time at which an agreement, treaty, or formal decision was officially approved and made valid.
-
D.
ratifiedAt
Indicates the date, time, or event context at which an agreement, treaty, or formal decision was officially ratified.
-
E.
obligationsOfSpain
Indicates that certain duties, responsibilities, or commitments are borne by Spain in a given context.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:39 p.m.