Triple
T29126684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: David vs. Goliath |
E738247
|
entity |
| Predicate | hasTribeSwap |
P195270
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Survivor: David vs. Goliath, hasTribeSwap, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribeSwap Context triple: [Survivor: David vs. Goliath, hasTribeSwap, yes]
-
A.
hasNonParticipantTribe
Indicates that a tribe is associated with a situation or event but does not actively participate in it.
-
B.
hasTribalPresence
Indicates that a tribal group is present, active, or represented in relation to the referenced entity or location.
-
C.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
D.
hasMergedTribe
Indicates that one tribe has combined or unified with another tribe to form a single merged group.
-
E.
usedByTribe
Indicates that something is utilized or employed by a particular tribe.
- F. None of above. chosen
Provenance (4 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_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
| PDg | Predicate description generation | batch_69fdb4544b548190b8971f8055d48caa |
completed | May 8, 2026, 10 a.m. |
Created at: April 28, 2026, 11:29 a.m.