Triple
T36973936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Delivery gold bars |
E914645
|
entity |
| Predicate | hasTypicalWeight |
P199545
|
FINISHED |
| Object | approximately 400 troy ounces |
—
|
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 400 troy ounces | Statement: [Good Delivery gold bars, hasTypicalWeight, approximately 400 troy ounces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalWeight Context triple: [Good Delivery gold bars, hasTypicalWeight, approximately 400 troy ounces]
-
A.
intendedWeight
Indicates the target or desired weight that an entity is meant or planned to have, rather than its current actual weight.
-
B.
hasTypicalMassProper
chosen
Indicates that an entity typically has a certain proper (inherent or characteristic) mass value associated with it.
-
C.
weightCondition
Indicates that a specified weight-related requirement or constraint holds between entities or values.
-
D.
hasTypicalStrength
Indicates that an entity possesses the usual or characteristic level of strength expected for its kind or context.
-
E.
weightStandardInfluencedBy
Indicates that a weight standard is affected, shaped, or determined by another factor, standard, or influence.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: May 3, 2026, 4:14 p.m.