Triple
T18402029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poor Knights Islands |
E450018
|
entity |
| Predicate | seaTemperature |
P9307
|
FINISHED |
| Object | relatively warm for latitude |
—
|
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: relatively warm for latitude | Statement: [Poor Knights Islands, seaTemperature, relatively warm for latitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaTemperature Context triple: [Poor Knights Islands, seaTemperature, relatively warm for latitude]
-
A.
waterTemperatureType
chosen
Indicates the classification or category of a water body’s temperature (e.g., cold, warm, hot) associated with an entity or context.
-
B.
seaDepth
Indicates the measured vertical distance from the sea surface down to the seafloor at a given location.
-
C.
waterTemperatureComparedTo
Indicates how the temperature of one body or sample of water compares to the temperature of another.
-
D.
seaType
Indicates the specific classification or category of a sea associated with an entity.
-
E.
requiresSeaSurfaceTemperature
Indicates that one entity depends on or needs a specified sea surface temperature condition to occur, function, or be valid.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e5195185b08190bd3b5471cdc047b0 |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.