Triple
T11022100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuujjuaq |
E260514
|
entity |
| Predicate | hasLong |
P96621
|
FINISHED |
| Object | cold winters |
—
|
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: cold winters | Statement: [Kuujjuaq, hasLong, cold winters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLong Context triple: [Kuujjuaq, hasLong, cold winters]
-
A.
hasLongBar
Indicates that an entity possesses or is associated with a bar that is long in length.
-
B.
hasLongStretchIn
Indicates that something extends for a considerable or continuous distance within a specified area, medium, or context.
-
C.
isLongRunning
Indicates that an action, process, or operation continues for an extended duration, typically longer than is usual or expected.
-
D.
hasLongChartRunIn
Indicates that something (typically a song, album, or similar work) remained on a specified chart for an extended, continuous period of time.
-
E.
hasMaxLengthApprox
Indicates that something has a maximum length that is approximately equal to a specified value, allowing for some tolerance or imprecision.
- F. None of above. chosen
Provenance (4 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797bd88188190a644adc9283cabb8 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:25 p.m.