Triple
T38650763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "It was a dark and stormy night" |
E939736
|
entity |
| Predicate | hasWeatherDescription |
P1702
|
FINISHED |
| Object | dark |
—
|
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: dark | Statement: ["It was a dark and stormy night", hasWeatherDescription, dark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeatherDescription Context triple: ["It was a dark and stormy night", hasWeatherDescription, dark]
-
A.
hasWeather
Indicates that a location or environment is experiencing or characterized by a particular type of weather condition.
-
B.
weatherCondition
chosen
Indicates the type of atmospheric state or weather pattern (e.g., sunny, rainy, snowy) affecting a location or time period.
-
C.
hasWeatherContext
Indicates that something is associated with, influenced by, or described in terms of specific weather conditions or patterns.
-
D.
weatherRole
Indicates a role or function that an entity has in relation to weather conditions or weather-related phenomena.
-
E.
allWeatherCapability
Indicates that an entity is capable of operating effectively under all weather conditions.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:33 p.m.