Triple
T26851865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maunder Minimum |
E676078
|
entity |
| Predicate | temporalLocationWithin |
P6261
|
FINISHED |
| Object | Little Ice Age |
—
|
NE NERFINISHED |
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: Little Ice Age | Statement: [Maunder Minimum, temporalLocationWithin, Little Ice Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalLocationWithin Context triple: [Maunder Minimum, temporalLocationWithin, Little Ice Age]
-
A.
hasTemporalLocation
Indicates that something occurs, exists, or is valid during a specific time or time interval.
-
B.
locatedAtTime
Indicates that a location relationship holds during a specific time or time interval.
-
C.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
D.
timePeriodWithin
chosen
Indicates that one time period is entirely contained within the bounds of another time period.
-
E.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61b924d0c819089d6f99cc09bbe59 |
completed | May 2, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:17 a.m.