Triple
T6645968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olonkinbyen |
E150699
|
entity |
| Predicate | hasPrimaryActivities |
P72016
|
FINISHED |
| Object | weather observation |
—
|
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: weather observation | Statement: [Olonkinbyen, hasPrimaryActivities, weather observation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryActivities Context triple: [Olonkinbyen, hasPrimaryActivities, weather observation]
-
A.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
B.
hasSignificantActivity
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
-
C.
hasPopularActivity
Indicates that an entity is associated with an activity that is widely favored, frequently engaged in, or well-liked by many people.
-
D.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
E.
hasPrimarySubject
Indicates that an entity is the main or principal subject associated with another entity or resource.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2 p.m.