Triple
T3403941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tappan Zee (wide section of the Hudson River) |
E71724
|
entity |
| Predicate | widerThan |
P10621
|
FINISHED |
| Object | upstream Hudson River channel |
—
|
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: upstream Hudson River channel | Statement: [Tappan Zee (wide section of the Hudson River), widerThan, upstream Hudson River channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widerThan Context triple: [Tappan Zee (wide section of the Hudson River), widerThan, upstream Hudson River channel]
-
A.
largerThan
chosen
Indicates that one entity has a greater size, extent, or magnitude than another entity.
-
B.
hasWidth
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
C.
width
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
D.
strongerThan
Indicates that one entity possesses greater strength, power, or intensity than another.
-
E.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8e8ea848190b4ac167f1aba8ebd |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.