Triple
T31493575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Treaty |
E803476
|
entity |
| Predicate | cededTerritoryToUnitedStates |
P171700
|
FINISHED |
| Object | East Florida |
—
|
NE NERFINISHED |
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: East Florida | Statement: [Florida Treaty, cededTerritoryToUnitedStates, East Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cededTerritoryToUnitedStates Context triple: [Florida Treaty, cededTerritoryToUnitedStates, East Florida]
-
A.
dateBecamePartOfUnitedStates
Indicates the date on which an entity formally became part of the United States.
-
B.
becamePartOfState
Indicates that an entity transitioned from a different status or jurisdiction to become incorporated into a particular state.
-
C.
establishedAsTerritory
Indicates that an entity was formally designated or recognized as a territory under the authority or control of another entity.
-
D.
succeededToStatehoodAs
Indicates that one entity became a sovereign state as the direct successor to another entity’s prior political or territorial status.
-
E.
adoptedBeforeIndependenceOf
Indicates that the adoption of one entity occurred prior to the independence event of another entity.
- F. None of above. chosen
Provenance (4 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_69f6a1e76f98819084babaa80607b5ed |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 30, 2026, 9:39 p.m.