Triple
T37512241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dry Steppes |
E932544
|
entity |
| Predicate | resourceAvailability |
P86514
|
FINISHED |
| Object | scarce water |
—
|
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: scarce water | Statement: [Dry Steppes, resourceAvailability, scarce water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceAvailability Context triple: [Dry Steppes, resourceAvailability, scarce water]
-
A.
resourceDepletionStatus
Indicates the current state or level of exhaustion of a particular resource, such as whether it is abundant, diminishing, or depleted.
-
B.
resourceStatus
chosen
Indicates the current condition or state of availability, usability, or operational readiness of a given resource.
-
C.
packageAvailability
Indicates whether a particular package is currently available for use, access, or distribution.
-
D.
resourceUsage
Indicates how much of a particular resource is consumed or utilized by an entity, process, or activity over a given context or period.
-
E.
initialAvailability
Indicates the starting level or state of availability of an entity before any changes or updates occur.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.