Triple
T16475062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Street, Jackson, Mississippi |
E400165
|
entity |
| Predicate | hasNearbyEntity |
P39585
|
FINISHED |
| Object | government buildings in downtown Jackson |
—
|
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: government buildings in downtown Jackson | Statement: [State Street, Jackson, Mississippi, hasNearbyEntity, government buildings in downtown Jackson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyEntity Context triple: [State Street, Jackson, Mississippi, hasNearbyEntity, government buildings in downtown Jackson]
-
A.
hasNotableNearbyEntity
chosen
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
B.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
C.
hasNearbyEvent
Indicates that an event occurs close in space or time to the referenced entity.
-
D.
hasNearbyPoint
Indicates that one entity has at least one other point located within a specified proximity or distance from it.
-
E.
hasNearbyEventType
Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32dd43cf88190881a5cbc80da1490 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.