Triple
T34587877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Deadly Shade of Gold |
E888092
|
entity |
| Predicate | characterRoleOfTravisMcGee |
P23263
|
FINISHED |
| Object | salvage consultant |
—
|
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: salvage consultant | Statement: [A Deadly Shade of Gold, characterRoleOfTravisMcGee, salvage consultant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterRoleOfTravisMcGee Context triple: [A Deadly Shade of Gold, characterRoleOfTravisMcGee, salvage consultant]
-
A.
roleInMysteryMen
Indicates that one entity has a specific role or part in the context of "Mystery Men," such as in its story, production, or related work.
-
B.
policeCharacter
Indicates that one entity serves as a police officer or law-enforcement figure in relation to another entity.
-
C.
actorForCharacterSheriffGilCorrigan
Indicates that an entity is the actor who portrays the character Sheriff Gil Corrigan.
-
D.
featuresCharacterRole
chosen
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
E.
roleInCreationOfGunsmoke
Indicates that an entity had a specific role or involvement in the creation or production of the work "Gunsmoke."
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: May 1, 2026, 2:03 a.m.