Triple
T5416585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolinian |
E121146
|
entity |
| Predicate | associatedDemonymCategory |
P191
|
FINISHED |
| Object | Demonyms for U.S. states |
—
|
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: Demonyms for U.S. states | Statement: [North Carolinian, associatedDemonymCategory, Demonyms for U.S. states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDemonymCategory Context triple: [North Carolinian, associatedDemonymCategory, Demonyms for U.S. states]
-
A.
relatedDemonym
Indicates that one entity is the demonym (name for residents or natives) associated with the other entity.
-
B.
hasDemonym
chosen
Indicates that one entity is the term (demonym) used to refer to the inhabitants or natives of another entity (typically a place).
-
C.
ethnicEponymOf
Indicates that one term is an eponym derived from or naming an ethnic group or people.
-
D.
ethnicCategoryIn
Indicates that an entity belongs to or is classified within a specified ethnic category in a given context.
-
E.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bff75881909bdfd2cdf7ff5657 |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.