Triple
T22086323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 12 |
E545784
|
entity |
| Predicate | passesThroughParish |
P146917
|
FINISHED |
| Object | East Baton Rouge Parish |
—
|
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: East Baton Rouge Parish | Statement: [Interstate 12, passesThroughParish, East Baton Rouge Parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passesThroughParish Context triple: [Interstate 12, passesThroughParish, East Baton Rouge Parish]
-
A.
parish
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
-
B.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
C.
usesParishSystem
Indicates that an entity organizes its local governance, administration, or jurisdiction according to a parish-based system.
-
D.
hasSettlementWithinParish
Indicates that a settlement is geographically located within the boundaries of a specific parish.
-
E.
parishesIncluded
Indicates that certain parishes are contained within, or form part of, a larger administrative, geographic, or organizational unit.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128ba24ac819082fc4aa274553481 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:29 p.m.