Triple
T3252612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shekel (weight-based) |
E68215
|
entity |
| Predicate | measuredWith |
P24236
|
FINISHED |
| Object | balance scales |
—
|
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: balance scales | Statement: [shekel (weight-based), measuredWith, balance scales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: measuredWith Context triple: [shekel (weight-based), measuredWith, balance scales]
-
A.
measuredBy
chosen
Indicates that something’s quantity, extent, or value is determined or expressed using a particular measurement method, instrument, or unit.
-
B.
measuredAs
Indicates that one entity’s quantity, value, or property is expressed or recorded using another entity as its measurement or unit.
-
C.
measured
Indicates that one entity has determined or quantified a property, amount, or extent of another entity using some standard or instrument.
-
D.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
E.
measuredFrom
Indicates that a measurement or value is determined relative to, or using, a specified reference point or source.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf440bb88190a2450405afae7f1f |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.