Triple
T11542951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reaper |
E273716
|
entity |
| Predicate | overwatchRoleColor |
P65114
|
FINISHED |
| Object | red |
—
|
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: red | Statement: [Reaper, overwatchRoleColor, red]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overwatchRoleColor Context triple: [Reaper, overwatchRoleColor, red]
-
A.
colourRole
chosen
Indicates that one entity serves a specific functional or contextual role defined in terms of colour in relation to another entity.
-
B.
teamColorContext
Indicates the contextual or situational association between a team and its designated color.
-
C.
teamColor
Indicates the association between a team and the color that represents or identifies it.
-
D.
leadCharacterColor
Indicates that one entity is the primary character and the other specifies the color associated with that lead character.
-
E.
introducedTeamColor
Indicates that an entity is responsible for introducing or establishing a particular team color for a team or 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e09eec8190894069d86b79183d |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.