Triple
T1063581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Oscillation |
E22959
|
entity |
| Predicate | quantifiedBy |
P4227
|
FINISHED |
| Object | pressure difference between Tahiti and Darwin |
—
|
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: pressure difference between Tahiti and Darwin | Statement: [Southern Oscillation, quantifiedBy, pressure difference between Tahiti and Darwin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quantifiedBy Context triple: [Southern Oscillation, quantifiedBy, pressure difference between Tahiti and Darwin]
-
A.
quantifies
chosen
Indicates that one entity expresses or specifies the amount, number, or degree of another entity.
-
B.
quantificationType
Indicates the specific kind or category of quantity or measurement being applied in a given context.
-
C.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
D.
isQuantumOf
Indicates that one entity represents a discrete, indivisible unit or packet of the other entity in a quantized relationship.
-
E.
determinedBy
Indicates that one entity’s state, value, or outcome is decided, controlled, or fully specified by 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f85cc08190ae03ac6c84936cc5 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b7359eb881909c868a558861cc18 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.