Triple
T28690192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Nicaragua |
E729255
|
entity |
| Predicate | initialTribeDivisionCriterion |
P166552
|
FINISHED |
| Object | age |
—
|
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: age | Statement: [Survivor: Nicaragua, initialTribeDivisionCriterion, age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialTribeDivisionCriterion Context triple: [Survivor: Nicaragua, initialTribeDivisionCriterion, age]
-
A.
tribeDivisionCriterion
chosen
Indicates the principle or basis by which a tribe is divided into its internal groups or segments.
-
B.
introducedTribe
Indicates that one entity caused a tribe to become known, present, or established to another entity or context for the first time.
-
C.
numberOfTribes
Indicates the total count of distinct tribes associated with a given entity or context.
-
D.
judgeFromTribe
Indicates that an individual serves as a judge who originates from or belongs to a particular tribe.
-
E.
divisionRaceContext
Indicates a contextual relationship where a division is characterized or defined in terms of a specific race or racial grouping.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 5:35 a.m.