Triple
T9125424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shwedagon Pagoda |
E218956
|
entity |
| Predicate | hasGemstones |
P38123
|
FINISHED |
| Object | diamonds |
—
|
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: diamonds | Statement: [Shwedagon Pagoda, hasGemstones, diamonds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGemstones Context triple: [Shwedagon Pagoda, hasGemstones, diamonds]
-
A.
stateGemstone
Indicates a relationship where a state is officially associated with or designated a particular gemstone.
-
B.
hasBirthstone
Indicates that a person or entity is associated with a particular gemstone traditionally recognized as their birthstone.
-
C.
containsGem
chosen
Indicates that one entity holds, encloses, or includes a gem within its boundaries or composition.
-
D.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
E.
hasRegionalStone
Indicates that something possesses or is associated with a characteristic stone specific to a particular region.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b8970881909c3b2c67fc131627 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.