Triple
T21881251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keeling Curve |
E540283
|
entity |
| Predicate | hasTemporalCoverageStart |
P88712
|
FINISHED |
| Object | March 1958 |
—
|
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: March 1958 | Statement: [Keeling Curve, hasTemporalCoverageStart, March 1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemporalCoverageStart Context triple: [Keeling Curve, hasTemporalCoverageStart, March 1958]
-
A.
hasTemporalEnd
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
B.
hasTemporalUse
Indicates that something is used, applicable, or valid only during a specific time or temporal interval.
-
C.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
D.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
E.
recordedInPeriodStart
chosen
Indicates that an event or record began or was first documented at the start of a specified time period.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118e7a3c48190be1cc285ad4b6496 |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:04 p.m.