Triple
T27225186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Chain across the Hudson River |
E681390
|
entity |
| Predicate | totalWeight |
P166644
|
FINISHED |
| Object | approximately 65 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: approximately 65 tons | Statement: [Great Chain across the Hudson River, totalWeight, approximately 65 tons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalWeight Context triple: [Great Chain across the Hudson River, totalWeight, approximately 65 tons]
-
A.
emptyWeight
Indicates the weight of an object or vehicle when it is empty, excluding any load, cargo, or passengers.
-
B.
totalEngineWeight
Indicates the combined weight of all engines associated with a given object or system.
-
C.
averageWeight
Indicates the typical or mean weight value associated with an entity or group of entities.
-
D.
weightsEnvironmentsBy
Indicates that one entity assigns or applies weights to different environments, influencing how each environment is considered or evaluated.
-
E.
availableWeights
Indicates that certain weight values or options are currently accessible or usable in a given context.
- F. None of above. chosen
Provenance (4 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 27, 2026, 9:44 a.m.