Triple
T21328977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureya River |
E525844
|
entity |
| Predicate | freezePeriod |
P110377
|
FINISHED |
| Object | November to late April |
—
|
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: November to late April | Statement: [Bureya River, freezePeriod, November to late April]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freezePeriod Context triple: [Bureya River, freezePeriod, November to late April]
-
A.
freezeUpPeriod
chosen
Indicates a time span during which something becomes or remains frozen and unable to move or function normally.
-
B.
thawPeriod
Indicates the time span during which something transitions from a frozen to an unfrozen state.
-
C.
dormancyPeriod
Indicates the length of time an entity remains inactive or in a dormant state before resuming activity.
-
D.
shutdownPeriod
Indicates a time interval during which a system, service, or process is intentionally turned off or not operational.
-
E.
hasFreezingPeriod
Indicates that an entity is subject to a defined time interval during which freezing (e.g., of assets, operations, or conditions) is in effect.
- 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7ab4f95fc819087eb32dca7da689a |
completed | April 21, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:42 p.m.