Triple
T23684530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamebred |
E585126
|
entity |
| Predicate | bearerEthnicBackground |
P194
|
FINISHED |
| Object | Cuban descent |
—
|
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: Cuban descent | Statement: [Gamebred, bearerEthnicBackground, Cuban descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerEthnicBackground Context triple: [Gamebred, bearerEthnicBackground, Cuban descent]
-
A.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
B.
laterEthnicIdentity
Indicates that an entity’s ethnic identity is associated with or applies to a later period in time relative to some earlier state or context.
-
C.
ethnicOrigin
chosen
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
D.
representedEthnicFirst
Indicates that an entity served as the first person of a given ethnic group to represent another entity (such as an institution, organization, or jurisdiction).
-
E.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4fb26c88190a6776e4dfd10d54c |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.