Triple
T31233014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaplan, Louisiana |
E796336
|
entity |
| Predicate | demographicsEthnicHeritage |
P194
|
FINISHED |
| Object | Acadian descendants |
—
|
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: Acadian descendants | Statement: [Kaplan, Louisiana, demographicsEthnicHeritage, Acadian descendants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demographicsEthnicHeritage Context triple: [Kaplan, Louisiana, demographicsEthnicHeritage, Acadian descendants]
-
A.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
B.
sharesEthnicity
Indicates that two entities belong to the same ethnic group or share the same ethnic background.
-
C.
ethnicOrigin
chosen
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
D.
EthnicaType
Indicates a relationship where an entity is classified according to a specific ethnic category or type.
-
E.
dominantEthnicGroups
Indicates that the specified ethnic groups hold primary demographic, cultural, or political prominence within a given region or population.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:10 p.m.