Triple
T1848493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Decadal Oscillation |
E41339
|
entity |
| Predicate | hasTemporalScale |
P9981
|
FINISHED |
| Object | decadal |
—
|
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: decadal | Statement: [Pacific Decadal Oscillation, hasTemporalScale, decadal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemporalScale Context triple: [Pacific Decadal Oscillation, hasTemporalScale, decadal]
-
A.
supportsTimescale
Indicates that one entity is capable of operating with, accommodating, or being compatible with a specified timescale or range of temporal resolutions.
-
B.
hasTemporalLocation
Indicates that something occurs, exists, or is valid during a specific time or time interval.
-
C.
supportsTimestamps
Indicates that the subject is capable of handling, storing, or recognizing timestamp information associated with relevant data or events.
-
D.
timescale
chosen
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
-
E.
hasScale
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.