Triple
T14656525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hombre (film) |
E344123
|
entity |
| Predicate | leadCharacterEthnicityContext |
P28254
|
FINISHED |
| Object | white man raised by Apaches |
—
|
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: white man raised by Apaches | Statement: [Hombre (film), leadCharacterEthnicityContext, white man raised by Apaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadCharacterEthnicityContext Context triple: [Hombre (film), leadCharacterEthnicityContext, white man raised by Apaches]
-
A.
leadActorEthnicity
Indicates the ethnic background or identity of the primary (lead) actor in a work.
-
B.
portrayedByEthnicity
Indicates that an entity is portrayed or represented by someone of a specified ethnic background.
-
C.
depictsEthnicContext
Indicates that one entity visually represents or portrays the ethnic background, identity, or cultural context associated with another entity.
-
D.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
-
E.
protagonistEthnicity
chosen
Indicates the ethnic background or cultural heritage associated with a work’s main character.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb51a562c819098971447db4b29f7 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.