Triple
T26576304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rapides Parish |
E666955
|
entity |
| Predicate | hasParishGovernmentSeat |
P179007
|
FINISHED |
| Object | Rapides Parish Courthouse |
—
|
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: Rapides Parish Courthouse | Statement: [Rapides Parish, hasParishGovernmentSeat, Rapides Parish Courthouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishGovernmentSeat Context triple: [Rapides Parish, hasParishGovernmentSeat, Rapides Parish Courthouse]
-
A.
isInParishSeat
Indicates that an entity is located within the administrative center (parish seat) of a given parish.
-
B.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
C.
hasMunicipalSeatFunction
Indicates that an entity serves as the administrative or municipal seat (central governing location) for a municipality.
-
D.
hasMunicipalLeaderSeat
Indicates that a specific location serves as the official seat or office location of a municipal leader (e.g., mayor) for a municipality.
-
E.
hasParishCouncils
Indicates that an entity possesses, is served by, or is administratively associated with one or more parish councils.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 27, 2026, 2 a.m.