Triple
T17690303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | grivna |
E441005
|
entity |
| Predicate | standardWeightApproximation |
P7301
|
FINISHED |
| Object | around 200 grams for some regional types |
—
|
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: around 200 grams for some regional types | Statement: [grivna, standardWeightApproximation, around 200 grams for some regional types]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardWeightApproximation Context triple: [grivna, standardWeightApproximation, around 200 grams for some regional types]
-
A.
approximateWeightInPounds
Indicates the estimated weight of an entity expressed in pounds, rather than an exact measured value.
-
B.
approximateMass
chosen
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
C.
averageWeight
Indicates the typical or mean weight value associated with an entity or group of entities.
-
D.
weightStandardInfluencedBy
Indicates that a weight standard is affected, shaped, or determined by another factor, standard, or influence.
-
E.
weightForAge
Indicates the weight measurement associated with an entity given its age.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704b43a88190ba29654ca695839e |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:03 a.m.