Triple
T7363658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Monument (Monas) |
E169812
|
entity |
| Predicate | goldPlatingWeight |
P77070
|
FINISHED |
| Object | approximately 35 kg |
—
|
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: approximately 35 kg | Statement: [National Monument (Monas), goldPlatingWeight, approximately 35 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goldPlatingWeight Context triple: [National Monument (Monas), goldPlatingWeight, approximately 35 kg]
-
A.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
B.
silverWeight
Indicates the weight or mass of an entity measured specifically in silver.
-
C.
previousGoldPurity
Indicates that one entity represents the gold purity value that applied to another entity at an earlier time or in a prior state.
-
D.
higherSilverContentThan
Indicates that one entity has a greater amount or proportion of silver content than another entity.
-
E.
caratWeight
Indicates the weight of a gemstone or diamond, measured in carats, associated with an item or entity.
- 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f26c050c8190a2d009b45d920490 |
completed | March 27, 2026, 9:11 p.m. |
Created at: March 27, 2026, 3:06 p.m.