Triple
T3862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson River |
E73
|
entity |
| Predicate | basinArea |
P175
|
FINISHED |
| Object | approximately 13,000 square miles |
—
|
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 13,000 square miles | Statement: [Hudson River, basinArea, approximately 13,000 square miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basinArea Context triple: [Hudson River, basinArea, approximately 13,000 square miles]
-
A.
landArea
Indicates the total surface area of a piece of land associated with an entity, typically measured in standardized units (e.g., square meters, hectares).
-
B.
area
chosen
Indicates that one entity has a measured two-dimensional extent or surface size quantified by another entity.
-
C.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
D.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
-
E.
GNISFeatureID
Indicates that an entity is associated with a specific identifier assigned by the U.S. Geological Survey’s Geographic Names Information System (GNIS) to uniquely reference a geographic feature.
- 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_69a238d6b47881909e68288aed2fd858 |
completed | Feb. 28, 2026, 12:37 a.m. |
| NER | Named-entity recognition | batch_69a23bcc8eb48190b897cc331563980a |
completed | Feb. 28, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_69a23994309081909ff3e869deef2156 |
completed | Feb. 28, 2026, 12:40 a.m. |
Created at: Feb. 28, 2026, 12:40 a.m.