Triple
T9209767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 295 (Florida) |
E221082
|
entity |
| Predicate | encirclesFeature |
P7850
|
FINISHED |
| Object | Jacksonville urban area |
—
|
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: Jacksonville urban area | Statement: [Interstate 295 (Florida), encirclesFeature, Jacksonville urban area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encirclesFeature Context triple: [Interstate 295 (Florida), encirclesFeature, Jacksonville urban area]
-
A.
enclosesArea
Indicates that one entity surrounds and contains a bounded region of space occupied or defined by another.
-
B.
partlyEncircles
Indicates that one entity surrounds another along a substantial but incomplete portion of its boundary or perimeter.
-
C.
surrounds
chosen
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
D.
encircledForce
Indicates that a military force is surrounded by enemy units, cutting off its movement or escape routes.
-
E.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
- 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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9b3c8c081909a688ce699928fc0 |
completed | April 1, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:26 p.m.