Triple
T29126686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: David vs. Goliath |
E738247
|
entity |
| Predicate | mergeTribeName |
P164880
|
FINISHED |
| Object | Kalokalo |
—
|
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: Kalokalo | Statement: [Survivor: David vs. Goliath, mergeTribeName, Kalokalo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergeTribeName Context triple: [Survivor: David vs. Goliath, mergeTribeName, Kalokalo]
-
A.
tribeName
chosen
Indicates the name assigned to a tribe in the relationship.
-
B.
tribeNamedAfter
Indicates that a tribe bears a name derived from or given in reference to a particular person, place, group, or concept.
-
C.
preMergeTribes
Indicates that two or more tribes existed separately before being combined into a single merged tribe.
-
D.
hasTribeCommonName
Indicates that two entities are related by the commonly used (vernacular) name of a tribe.
-
E.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 11:29 a.m.