Triple
T15984052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kachin Independence Organization |
E387645
|
entity |
| Predicate | naturalResourceInvolved |
P68054
|
FINISHED |
| Object | jade |
—
|
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: jade | Statement: [Kachin Independence Organization, naturalResourceInvolved, jade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: naturalResourceInvolved Context triple: [Kachin Independence Organization, naturalResourceInvolved, jade]
-
A.
naturalResources
Indicates that one entity possesses, contains, or is a source of natural resources for another entity.
-
B.
usesNaturalResource
Indicates that an entity makes use of a natural resource (such as water, minerals, or forests) to support its activities, processes, or functions.
-
C.
naturalOccurrence
Indicates that the related event or phenomenon happens in nature without direct human intervention or artificial cause.
-
D.
hasGeologicResource
chosen
Indicates that an entity possesses, contains, or is associated with a particular geologic resource.
-
E.
hasNaturalFeature
Indicates that one entity possesses, contains, or is characterized by a particular natural feature (such as a mountain, river, forest, or coastline).
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.