Triple
T9125419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shwedagon Pagoda |
E218956
|
entity |
| Predicate | estimatedGoldWeight |
P77070
|
FINISHED |
| Object | over 20,000 bars of gold leaf |
—
|
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: over 20,000 bars of gold leaf | Statement: [Shwedagon Pagoda, estimatedGoldWeight, over 20,000 bars of gold leaf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedGoldWeight Context triple: [Shwedagon Pagoda, estimatedGoldWeight, over 20,000 bars of gold leaf]
-
A.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
B.
goldPlatingWeight
chosen
Indicates the weight associated with a layer or amount of gold plating applied to an object or surface.
-
C.
silverWeight
Indicates the weight or mass of an entity measured specifically in silver.
-
D.
caratWeight
Indicates the weight of a gemstone or diamond, measured in carats, associated with an item or entity.
-
E.
ratioToGold
Indicates the proportional relationship between a given quantity and a corresponding amount of gold.
- 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.