Triple

T18868789
Position Surface form Disambiguated ID Type / Status
Subject Yenangyaung E461511 entity
Predicate hasLocalEconomyResource P25525 FINISHED
Object onshore oil 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: onshore oil | Statement: [Yenangyaung, hasLocalEconomyResource, onshore oil]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalEconomyResource
Context triple: [Yenangyaung, hasLocalEconomyResource, onshore oil]
  • A. hasEconomicResource chosen
    Indicates that an entity possesses, controls, or has access to an economic resource (such as money, assets, or productive means) that can be used for economic activities or value creation.
  • B. hasEconomyCharacteristic
    Indicates that an economy possesses a particular attribute, feature, or quality.
  • C. hasNaturalResourceConstraint
    Indicates that an entity is subject to limitations or restrictions arising from the availability, quality, or sustainability of natural resources.
  • D. hasNearbyEconomicRegion
    Indicates that one economic region is geographically close to or adjacent to another economic region.
  • E. hasResourcePotential
    Indicates that an entity possesses the capacity or suitability to provide, generate, or support a particular resource in the future.
  • 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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c2a7e1308190a1667d2d2d43df6c completed April 20, 2026, 6:07 a.m.
PD Predicate disambiguation batch_69e48d2166b88190add38de96cedc65c completed April 19, 2026, 8:06 a.m.
Created at: April 10, 2026, 11:57 a.m.