Triple
T206579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Meridional Overturning Circulation |
E4621
|
entity |
| Predicate | monitoredAt |
P7677
|
FINISHED |
| Object | 26.5°N RAPID array |
—
|
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: 26.5°N RAPID array | Statement: [Atlantic Meridional Overturning Circulation, monitoredAt, 26.5°N RAPID array]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitoredAt Context triple: [Atlantic Meridional Overturning Circulation, monitoredAt, 26.5°N RAPID array]
-
A.
measuredAt
Indicates the time or point at which a measurement was taken or recorded for an entity or event.
-
B.
observedAt
chosen
Indicates that an entity was recorded or noticed at a specific time or place.
-
C.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
D.
displayedAt
Indicates that one entity is presented or exhibited at a particular location, venue, or event.
-
E.
immediateCauseDate
Indicates the specific date on which an event or condition directly caused another event or outcome to occur.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.