Triple
T5046976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Slave Lake |
E113689
|
entity |
| Predicate | frozenPeriod |
P14991
|
FINISHED |
| Object | typically frozen from November to May |
—
|
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: typically frozen from November to May | Statement: [Great Slave Lake, frozenPeriod, typically frozen from November to May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frozenPeriod Context triple: [Great Slave Lake, frozenPeriod, typically frozen from November to May]
-
A.
frozenFrom
chosen
Indicates that one entity has been preserved or immobilized by being frozen starting from another entity, source, or prior state.
-
B.
frozenIn
Indicates that one entity is immobilized or preserved in a solid, frozen state within or by another entity.
-
C.
registrationPeriod
Indicates the time span during which registration for something is open or valid.
-
D.
banPeriodEnd
Indicates the point in time when a ban or prohibition on an entity or action is scheduled to end.
-
E.
banPeriodStart
Indicates the date or time at which a ban or prohibition begins to take 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd740002b48190bc7aa176d734c589 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.