Triple
T32506249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grayson, Louisiana |
E830803
|
entity |
| Predicate | hasParishSeatNearby |
P198827
|
FINISHED |
| Object | Columbia, Louisiana |
—
|
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: Columbia, Louisiana | Statement: [Grayson, Louisiana, hasParishSeatNearby, Columbia, Louisiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishSeatNearby Context triple: [Grayson, Louisiana, hasParishSeatNearby, Columbia, Louisiana]
-
A.
hasMunicipalitySeatNearby
Indicates that the municipality’s administrative seat is located in close proximity to the referenced place or entity.
-
B.
parishSeatDistance
Indicates the distance between a parish and its designated parish seat (administrative center).
-
C.
nearParish
Indicates that one entity is geographically close to or in the vicinity of a specified parish.
-
D.
isParishSeatOf
Indicates that a location serves as the administrative center or main seat of government for a particular parish.
-
E.
isMunicipalityNear
Indicates that one municipality is located close to another municipality or geographic reference point.
- F. None of above. chosen
Provenance (4 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69ff0d800ee88190835e233d9e846cdb |
completed | May 9, 2026, 10:33 a.m. |
Created at: May 1, 2026, 1 a.m.