Triple
T29745796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Carroll Parish |
E752746
|
entity |
| Predicate | isInParishSystem |
P85718
|
FINISHED |
| Object | Louisiana parish system |
—
|
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: Louisiana parish system | Statement: [West Carroll Parish, isInParishSystem, Louisiana parish system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInParishSystem Context triple: [West Carroll Parish, isInParishSystem, Louisiana parish system]
-
A.
usesParishSystem
chosen
Indicates that an entity organizes its local governance, administration, or jurisdiction according to a parish-based system.
-
B.
hasParishType
Indicates that an entity is associated with or classified by a specific type or category of parish.
-
C.
hasParishJurisdiction
Indicates that one entity holds official parish-level authority or administrative control over another entity or area.
-
D.
isParishEquivalent
Indicates that one administrative or ecclesiastical unit is considered equivalent in status or function to a parish.
-
E.
isInCountryParishCluster
Indicates that an entity is located within, or belongs to, a specific parish-level geographic cluster inside a country.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67366211c8190b035057fa2665bf7 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:50 p.m.