Triple
T31493579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Treaty |
E803476
|
entity |
| Predicate | definedUSSpainBoundaryAlong |
P134024
|
FINISHED |
| Object | Sabine River |
—
|
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: Sabine River | Statement: [Florida Treaty, definedUSSpainBoundaryAlong, Sabine River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedUSSpainBoundaryAlong Context triple: [Florida Treaty, definedUSSpainBoundaryAlong, Sabine River]
-
A.
borderTypeWithSpain
Indicates the type or nature of the border that an entity shares with Spain.
-
B.
geographicBoundary
Indicates that one entity serves as a limiting border or edge that defines the geographic extent or separation of another entity.
-
C.
borderTypeWithGibraltar
Indicates the specific type or nature of the border relationship that an entity has with Gibraltar.
-
D.
boundaryUnit
chosen
Indicates that one entity serves as a boundary-defining unit or segment that delimits the extent or limits of another entity.
-
E.
languageAlongBorder
Indicates that a particular language is spoken or prevalent along the border between two regions or entities.
- 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_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 30, 2026, 9:39 p.m.