Triple
T618066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sentinelese |
E14448
|
entity |
| Predicate | relatedGroups |
P37
|
FINISHED |
| Object | other Andamanese peoples |
—
|
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: other Andamanese peoples | Statement: [Sentinelese, relatedGroups, other Andamanese peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedGroups Context triple: [Sentinelese, relatedGroups, other Andamanese peoples]
-
A.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
C.
relatedService
Indicates that one service is connected or associated with another service in a relevant or dependent way.
-
D.
socialGroupInvolved
Indicates that a particular social group participates in, is affected by, or is otherwise involved in the specified event or situation.
-
E.
relatedDivision
Indicates that there is an organizational or structural association between two divisions, such as being counterparts, partners, or otherwise linked within a broader entity.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e2418c881908552d2c4a5006e97 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfd15288190b4abdbd0bce3edcd |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.