Triple
T485630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neva River |
E9869
|
entity |
| Predicate | averageDischarge |
P5503
|
FINISHED |
| Object | approximately 2500 m³/s |
—
|
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 2500 m³/s | Statement: [Neva River, averageDischarge, approximately 2500 m³/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageDischarge Context triple: [Neva River, averageDischarge, approximately 2500 m³/s]
-
A.
waterFlowRate
chosen
Indicates the rate at which water moves or is transported through a given point or system over time.
-
B.
annualCapacity
Indicates the maximum amount of output or throughput an entity can produce or handle within a one-year period.
-
C.
averageSpreadingRate
Indicates the typical rate at which something (such as a phenomenon, substance, or influence) expands or propagates over a given distance or time.
-
D.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
E.
averageSlipRate
Indicates the typical rate at which displacement or movement occurs along a fault or interface over a specified period of time.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0bb46788190b40182bf2a54f98f |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf48ec08190b85d07e194f99c49 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.