Triple
T35688923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kachin conflict |
E1031233
|
entity |
| Predicate | hasResourceDimension |
P207094
|
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 conflict, hasResourceDimension, jade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResourceDimension Context triple: [Kachin conflict, hasResourceDimension, jade]
-
A.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
-
B.
hasDimensionProperty
Indicates that an entity is associated with a specific dimensional characteristic, such as size, length, width, height, or similar measurable extent.
-
C.
hasDimensionality
Indicates that an entity possesses a specific number of dimensions or a particular dimensional structure.
-
D.
hasResourceConstraint
Indicates that an entity is subject to a limitation or restriction on the resources it can use or access.
-
E.
hasScalingDimension
Indicates that an entity is associated with a specific scaling dimension, expressing how it transforms under changes of scale.
- F. None of above. chosen
Provenance (4 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:05 p.m.