Triple
T4762818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shompen language |
E105735
|
entity |
| Predicate | associatedPeopleStatus |
P59172
|
FINISHED |
| Object | indigenous people of Great Nicobar |
—
|
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: indigenous people of Great Nicobar | Statement: [Shompen language, associatedPeopleStatus, indigenous people of Great Nicobar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPeopleStatus Context triple: [Shompen language, associatedPeopleStatus, indigenous people of Great Nicobar]
-
A.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
B.
associationStatus
Indicates the current state or condition of an established association or relationship between entities.
-
C.
associatedState
Indicates that one entity is linked or connected to a particular state, condition, or status of another entity.
-
D.
associatedFort
Indicates that one entity is connected or linked to a particular fort, typically as its related or corresponding fortification.
-
E.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd686dc7b88190b41e8a362701080d |
completed | March 20, 2026, 3:31 p.m. |
Created at: March 20, 2026, 1:20 p.m.