Triple
T24505380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandhill |
E618050
|
entity |
| Predicate | locatedOnMainRouteBetween |
P68000
|
FINISHED |
| Object | Belize City |
—
|
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: Belize City | Statement: [Sandhill, locatedOnMainRouteBetween, Belize City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnMainRouteBetween Context triple: [Sandhill, locatedOnMainRouteBetween, Belize City]
-
A.
locatedOnRouteTo
chosen
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
B.
locatedBetweenStreets
Indicates that something is situated between two specified streets, with its position bounded or defined by those streets.
-
C.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
D.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
E.
includesRouteBetween
Indicates that one entity (such as a service, plan, or network) contains or provides a specific route connecting two locations or points.
- 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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.