Triple
T6777028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resígaro language |
E155582
|
entity |
| Predicate | vitalityTrend |
P5318
|
FINISHED |
| Object | declining |
—
|
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: declining | Statement: [Resígaro language, vitalityTrend, declining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vitalityTrend Context triple: [Resígaro language, vitalityTrend, declining]
-
A.
trends
Indicates that one entity exhibits a general direction of change or development over time in relation to another reference or context.
-
B.
hasTrend
chosen
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
C.
healthIndicator
Indicates a measure or signal that reflects the health status or condition of an entity.
-
D.
treeVigor
Indicates the overall health, strength, and growth potential of a tree based on its physiological condition and environmental factors.
-
E.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26725208190b64935cfd08b2aff |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:13 p.m.