Triple
T29126620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Samoa |
E738246
|
entity |
| Predicate | mergedTribe |
P166970
|
FINISHED |
| Object | Aiga |
—
|
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: Aiga | Statement: [Survivor: Samoa, mergedTribe, Aiga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedTribe Context triple: [Survivor: Samoa, mergedTribe, Aiga]
-
A.
mergedColonies
Indicates that two or more previously separate colonies have been combined into a single unified colony.
-
B.
inTribe
Indicates that an entity belongs to, is a member of, or is affiliated with a particular tribe.
-
C.
introducedTribe
Indicates that one entity caused a tribe to become known, present, or established to another entity or context for the first time.
-
D.
preMergeTribes
chosen
Indicates that two or more tribes existed separately before being combined into a single merged tribe.
-
E.
tribeConfederation
Indicates a relationship where multiple tribes are united or organized together into a larger confederated group or alliance.
- 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_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 11:29 a.m.