Triple
T38497202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skógafoss |
E919725
|
entity |
| Predicate | spray |
P101037
|
FINISHED |
| Object | heavy mist near base |
—
|
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: heavy mist near base | Statement: [Skógafoss, spray, heavy mist near base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spray Context triple: [Skógafoss, spray, heavy mist near base]
-
A.
hasSpray
Indicates that one entity possesses, contains, or is equipped with a spray or spraying capability in relation to another entity or context.
-
B.
sprayHeight
Indicates the vertical distance or elevation at which a spray (such as liquid, particles, or mist) is emitted or reaches.
-
C.
spouts
Indicates the action of forcefully ejecting or emitting something, typically in a sudden stream or jet, from one entity toward its surroundings.
-
D.
blows
Indicates that one entity forcefully expels air or creates a current of air directed toward or acting upon another entity.
-
E.
producesAerosol
chosen
Indicates that one entity generates or emits an aerosol (a suspension of fine solid particles or liquid droplets in air) as a result of its action or process.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.