Triple
T26133259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monas |
E659307
|
entity |
| Predicate | topDecorationGoldWeight |
P160724
|
FINISHED |
| Object | approximately 50 kilograms |
—
|
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 50 kilograms | Statement: [Monas, topDecorationGoldWeight, approximately 50 kilograms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topDecorationGoldWeight Context triple: [Monas, topDecorationGoldWeight, approximately 50 kilograms]
-
A.
topDecorationWeight
chosen
Indicates the weight or mass of the decorative element located at the top of an object or structure.
-
B.
goldPlatingWeight
Indicates the weight associated with a layer or amount of gold plating applied to an object or surface.
-
C.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
D.
goldDescribedAs
Indicates that something is characterized or referred to using the term "gold" or a gold-related description.
-
E.
numberOfDecorativeJewels
Indicates the count of decorative jewels associated with or present on a given entity.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 8:16 p.m.