Triple
T31493583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Treaty |
E803476
|
entity |
| Predicate | definedUSSpainBoundaryRegion |
P108932
|
FINISHED |
| Object | Louisiana Purchase |
—
|
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: Louisiana Purchase | Statement: [Florida Treaty, definedUSSpainBoundaryRegion, Louisiana Purchase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedUSSpainBoundaryRegion Context triple: [Florida Treaty, definedUSSpainBoundaryRegion, Louisiana Purchase]
-
A.
mainRegionInSpain
Indicates that a location is the primary or most significant region associated with a place or entity within Spain.
-
B.
borderTypeWithSpain
Indicates the type or nature of the border that an entity shares with Spain.
-
C.
otherDOCaRegionInSpain
Indicates that one document is about a region located in Spain, while the other document concerns a different region within Spain.
-
D.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
E.
geographicBoundary
chosen
Indicates that one entity serves as a limiting border or edge that defines the geographic extent or separation of another entity.
- 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_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 30, 2026, 9:39 p.m.