Triple
T36381039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Heroes vs. Villains |
E896046
|
entity |
| Predicate | tribeDivisionTheme |
P164880
|
FINISHED |
| Object | Heroes vs. Villains |
—
|
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 vs. Villains | Statement: [Survivor: Heroes vs. Villains, tribeDivisionTheme, Heroes vs. Villains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribeDivisionTheme Context triple: [Survivor: Heroes vs. Villains, tribeDivisionTheme, Heroes vs. Villains]
-
A.
tribeDivisionCriterion
Indicates the principle or basis by which a tribe is divided into its internal groups or segments.
-
B.
tribeName
chosen
Indicates the name assigned to a tribe in the relationship.
-
C.
tribeCharacterization
Indicates how a tribe or tribal group is characterized or described in terms of its defining qualities, attributes, or identity.
-
D.
tribalRoll
Indicates a roll or rotation action performed in a manner characteristic of or associated with a tribe or tribal context.
-
E.
tribeLed
Indicates that one entity serves as the leader or ruling authority over a particular tribe.
- 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.