Triple
T34901082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Feliciana Parish |
E1006588
|
entity |
| Predicate | hasCountyEquivalentStatusIn |
P100479
|
FINISHED |
| Object | United States Census Bureau |
E2037
|
NE 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: United States Census Bureau | Statement: [East Feliciana Parish, hasCountyEquivalentStatusIn, United States Census Bureau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyEquivalentStatusIn Context triple: [East Feliciana Parish, hasCountyEquivalentStatusIn, United States Census Bureau]
-
A.
hasCountyEquivalentStatus
chosen
Indicates that an entity holds an administrative or legal status equivalent to that of a county within a given jurisdiction.
-
B.
hasCountyTopStatus
Indicates that an entity holds the highest or most prominent status within a specific county.
-
C.
hasCountyCode
Indicates that an entity is associated with a specific county identified by a standardized county code.
-
D.
isNamedCountyOf
Indicates that a county bears a specific official name within a given jurisdiction or context.
-
E.
hasCountyAdministration
Indicates that an entity is governed, managed, or served by a specific county-level administrative authority.
- F. None of above.
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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3786ea48248190bdab48fed5f0dd73 |
completed | June 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.