Triple
T34995171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun, Louisiana |
E1009506
|
entity |
| Predicate | isInParishGovernment |
P172569
|
FINISHED |
| Object | St. Tammany Parish Government |
—
|
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: St. Tammany Parish Government | Statement: [Sun, Louisiana, isInParishGovernment, St. Tammany Parish Government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInParishGovernment Context triple: [Sun, Louisiana, isInParishGovernment, St. Tammany Parish Government]
-
A.
hasParishGovernmentSeat
Indicates that a parish serves as the administrative or governmental seat for a specified jurisdiction or governing body.
-
B.
isInParishSeat
chosen
Indicates that an entity is located within the administrative center (parish seat) of a given parish.
-
C.
isLocalGovernment
Indicates that an entity functions as a governing body with authority over a specific local or regional area within a larger political system.
-
D.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
E.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.