Triple
T27225185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Chain across the Hudson River |
E681390
|
entity |
| Predicate | linkWeight |
P144607
|
FINISHED |
| Object | approximately 100 to 180 pounds per link |
—
|
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 100 to 180 pounds per link | Statement: [Great Chain across the Hudson River, linkWeight, approximately 100 to 180 pounds per link]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkWeight Context triple: [Great Chain across the Hudson River, linkWeight, approximately 100 to 180 pounds per link]
-
A.
linkType
Indicates the specific kind or category of relationship that connects two linked entities.
-
B.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
-
C.
edgeWeights
chosen
Indicates a relationship where each edge in a graph is associated with a specific numerical weight or cost.
-
D.
linkRole
Indicates a role or function that an entity plays within a specific link or relationship between entities.
-
E.
linkedIndicator
Indicates that one indicator is associated with, derived from, or otherwise connected to another indicator.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6264a03648190a9b6904ce2f7aeeb |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:44 a.m.