Triple
T18353910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Warner |
E439739
|
entity |
| Predicate | hasEthnicCultureFocus |
P98449
|
FINISHED |
| Object | Appalachian culture |
—
|
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: Appalachian culture | Statement: [Frank Warner, hasEthnicCultureFocus, Appalachian culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicCultureFocus Context triple: [Frank Warner, hasEthnicCultureFocus, Appalachian culture]
-
A.
hasEthnicScope
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
-
B.
hasEthnicInfluence
Indicates that one entity has a cultural, traditional, or ethnic impact on, or contributes to shaping the ethnic character of, another entity.
-
C.
primaryEthnicFocus
chosen
Indicates that something is chiefly oriented toward, concerned with, or designed for a particular ethnic group as its main focus.
-
D.
hasCulturalRoots
Indicates that something originates from, is shaped by, or is deeply connected to particular cultural traditions, practices, or heritage.
-
E.
hasEthnicTarget
Indicates that an action, statement, or event is directed toward or targets a specific ethnic group.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516d37bc08190abc9b4e8c937c914 |
completed | April 19, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.