Triple
T3698422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sentinelese language |
E78512
|
entity |
| Predicate | contactWithResearchers |
P49456
|
FINISHED |
| Object | minimal |
—
|
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: minimal | Statement: [Sentinelese language, contactWithResearchers, minimal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contactWithResearchers Context triple: [Sentinelese language, contactWithResearchers, minimal]
-
A.
researchUser
Indicates that an entity conducts research on, studies, or investigates a particular user.
-
B.
alsoServesResearchersFrom
Indicates that, in addition to its primary audience, an entity provides services or support to researchers from the specified other entity or location.
-
C.
hasResearcher
Indicates that an entity is associated with or linked to a specific researcher responsible for work, study, or investigation related to it.
-
D.
conductsResearchAt
Indicates that a subject carries out research activities at a specified institution, organization, or location.
-
E.
usesResearchSubject
Indicates that one entity employs or utilizes another entity as a research subject in a study or investigation.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc512ba188190a15bcacafac3f476 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb903be308190a8f1925f99e67c68 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:26 p.m.