Triple
T4564779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multivariate ENSO Index |
E121882
|
entity |
| Predicate | referencePeriod |
P4343
|
FINISHED |
| Object | 1950–1993 (original MEI) |
—
|
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: 1950–1993 (original MEI) | Statement: [Multivariate ENSO Index, referencePeriod, 1950–1993 (original MEI)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referencePeriod Context triple: [Multivariate ENSO Index, referencePeriod, 1950–1993 (original MEI)]
-
A.
refersToPeriod
chosen
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
aboutPeriod
Indicates that something (such as a work, record, or statement) concerns or pertains to a specific time period.
-
D.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
-
E.
focusPeriodEnd
Indicates the point in time at which a specified focus period or interval concludes.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589b439c81908da9d19433310bcd |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.