Triple
T12924484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wisconsin Stage |
E309208
|
entity |
| Predicate | timeSpanEndApprox |
P35787
|
FINISHED |
| Object | about 11,000 years ago |
—
|
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: about 11,000 years ago | Statement: [Wisconsin Stage, timeSpanEndApprox, about 11,000 years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanEndApprox Context triple: [Wisconsin Stage, timeSpanEndApprox, about 11,000 years ago]
-
A.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
B.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
C.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
D.
endTimeApproximate
chosen
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
typicalEndDateRange
Indicates the usual or expected range of end dates associated with an event, activity, or time-bounded entity.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e9576c81908eb59569af6da877 |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fab4d0881909a7a4d66bab9aa85 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.