Triple
T38416981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan of Bronze |
E903125
|
entity |
| Predicate | hasEthnicBackgroundOfReferent |
P159764
|
FINISHED |
| Object | Afro-Cuban |
—
|
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: Afro-Cuban | Statement: [Titan of Bronze, hasEthnicBackgroundOfReferent, Afro-Cuban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicBackgroundOfReferent Context triple: [Titan of Bronze, hasEthnicBackgroundOfReferent, Afro-Cuban]
-
A.
hasEthnicOrRegionalOrigin
chosen
Indicates that an entity originates from, or is associated with, a particular ethnic group or geographic region.
-
B.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
-
C.
hasEthnicScope
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
-
D.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
-
E.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
- 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 3, 2026, 4:31 p.m.