Triple
T33912241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junebug |
E869346
|
entity |
| Predicate | hasEthnicityContext |
P27835
|
FINISHED |
| Object | African-American |
—
|
NE NERFINISHED |
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: African-American | Statement: [Junebug, hasEthnicityContext, African-American]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicityContext Context triple: [Junebug, hasEthnicityContext, African-American]
-
A.
hasEthnolinguisticContext
Indicates that something is associated with, shaped by, or understood within a specific ethnolinguistic (cultural and language-based) context.
-
B.
hasEthnicScope
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
-
C.
hasEthnicCharacteristic
chosen
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
-
D.
hasEthnicCore
Indicates that an entity possesses a central or defining ethnic group that forms the core of its identity or composition.
-
E.
hasEthnicGroupType
Indicates that an entity is associated with, characterized by, or classified according to a particular type or category of 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:48 a.m.