Triple
T29495221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Kaôh Rōng |
E748200
|
entity |
| Predicate | tribeDivision |
P13151
|
FINISHED |
| Object | Brains tribe |
—
|
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: Brains tribe | Statement: [Survivor: Kaôh Rōng, tribeDivision, Brains tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribeDivision Context triple: [Survivor: Kaôh Rōng, tribeDivision, Brains tribe]
-
A.
tribeDivisionCriterion
Indicates the principle or basis by which a tribe is divided into its internal groups or segments.
-
B.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
C.
tribeInheritanceRegion
Indicates the geographic region or area from which a tribe’s inheritance, territory, or ancestral land is derived or associated.
-
D.
regionDivision
Indicates a hierarchical or organizational subdivision relationship where one region is partitioned into smaller constituent regions.
-
E.
tribeOrGens
chosen
Indicates a relationship where an entity belongs to, is associated with, or is identified as a particular tribe or gens (clan/lineage group).
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c0e07e48190a1a5554455766b30 |
completed | May 2, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 4:18 p.m.