Triple
T29112747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Heroes vs. Healers vs. Hustlers |
E736956
|
entity |
| Predicate | tribeTheme |
P25955
|
FINISHED |
| Object | Heroes |
—
|
NE NERFINISHED |
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: Heroes | Statement: [Survivor: Heroes vs. Healers vs. Hustlers, tribeTheme, Heroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribeTheme Context triple: [Survivor: Heroes vs. Healers vs. Hustlers, tribeTheme, Heroes]
-
A.
transformationTheme
Indicates a thematic relationship in which one entity centers on or explores the process, experience, or idea of transformation in another.
-
B.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
C.
flavorTheme
Indicates a relationship where one entity serves as the dominant or characteristic flavor profile guiding or defining the taste experience of another entity.
-
D.
impliesTheme
Indicates that one entity conceptually suggests, hints at, or leads to the thematic presence of another entity.
-
E.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:19 a.m.