Triple
T4762805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shompen language |
E105735
|
entity |
| Predicate | vitality |
P40685
|
FINISHED |
| Object | severely threatened |
—
|
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: severely threatened | Statement: [Shompen language, vitality, severely threatened]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vitality Context triple: [Shompen language, vitality, severely threatened]
-
A.
strength
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
-
B.
energyLevel
chosen
Indicates the amount or intensity of energy possessed, produced, or exhibited by an entity in a given state or context.
-
C.
virtue
Indicates that an entity possesses or exemplifies a morally good quality, trait, or behavior.
-
D.
volatility
Indicates that the degree of variability or instability in the related entity’s value, state, or behavior is being characterized.
-
E.
endurance
Indicates the capacity of an entity to sustain an activity, state, or condition over an extended period without failure or significant loss of performance.
- 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_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. |
Created at: March 20, 2026, 1:20 p.m.