Triple
T21784253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erie Canal weighlock |
E537793
|
entity |
| Predicate | usedMeasurementUnit |
P12631
|
FINISHED |
| Object | tons |
—
|
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: tons | Statement: [Erie Canal weighlock, usedMeasurementUnit, tons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMeasurementUnit Context triple: [Erie Canal weighlock, usedMeasurementUnit, tons]
-
A.
unitOfMeasure
chosen
Indicates that one entity specifies the standard unit in which the quantity or value of another entity is measured.
-
B.
usesMeasurementSystem
Indicates that one entity adopts or applies a particular system of measurement defined by another entity.
-
C.
typeOfMeasure
Indicates that one entity specifies the kind or category of measurement used to quantify or evaluate another entity.
-
D.
usedAsNaturalUnitIn
Indicates that something functions as a standard or reference unit for measuring or quantifying another thing within a natural or intrinsic context.
-
E.
usesMetric
Indicates that one entity adopts, applies, or relies on a particular metric or measurement standard in its operation, evaluation, or description.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f046303d54819096b3fab4ab5678e6 |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.