Triple
T16542480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe/Warsaw |
E401852
|
entity |
| Predicate | dstObservationPeriod |
P302
|
FINISHED |
| Object | from late March to late October |
—
|
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: from late March to late October | Statement: [Europe/Warsaw, dstObservationPeriod, from late March to late October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dstObservationPeriod Context triple: [Europe/Warsaw, dstObservationPeriod, from late March to late October]
-
A.
dstObserved
Indicates that an entity has been observed, detected, or recorded as the destination of another entity or action.
-
B.
focusPeriodEnd
Indicates the point in time at which a specified focus period or interval concludes.
-
C.
timePeriodOrigin
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
D.
dstObservedHistorically
Indicates that something has been observed or recorded at a particular destination or location in the past.
-
E.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3455db6788190b929546050ea2488 |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.