Triple
T791460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarawa |
E16922
|
entity |
| Predicate | healthRisk |
P3842
|
FINISHED |
| Object | high vulnerability to introduced diseases |
—
|
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: high vulnerability to introduced diseases | Statement: [Jarawa, healthRisk, high vulnerability to introduced diseases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthRisk Context triple: [Jarawa, healthRisk, high vulnerability to introduced diseases]
-
A.
healthProxy
Indicates that one entity is authorized to make health-related or medical decisions on behalf of another entity.
-
B.
riskFeature
Indicates that one entity possesses or exhibits a characteristic, condition, or attribute that increases the likelihood or severity of a negative outcome for another entity or situation.
-
C.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
D.
hasHealthConcern
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
-
E.
riskLevel
chosen
Indicates the degree of potential harm, loss, or adverse outcome associated with a particular situation, action, or 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a798c7608190b9c79c52a1fe0859 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50ef72c819084ffe9f31dbd0262 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.