Triple
T2032367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yonne |
E44545
|
entity |
| Predicate | hasBasinArea |
P1641
|
FINISHED |
| Object | about 10,800 km² |
—
|
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: about 10,800 km² | Statement: [Yonne, hasBasinArea, about 10,800 km²]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasinArea Context triple: [Yonne, hasBasinArea, about 10,800 km²]
-
A.
drainageBasinArea
chosen
Indicates the total surface area of land from which precipitation and runoff drain into a particular water body or watershed.
-
B.
hasBasinPopulation
Indicates that a geographic basin is associated with a specific number of inhabitants living within its area.
-
C.
watershedArea
Indicates the total land area from which surface water drains into a particular water body or point in the drainage system.
-
D.
locatedInBasin
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
-
E.
drainageAreaApprox
Indicates that one entity has an approximate drainage area measured or characterized by the other entity.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9313134819088133fb69b8f606f |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.