Triple
T31311145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tout |
E798464
|
entity |
| Predicate | approximateGregorianEnd |
P35259
|
FINISHED |
| Object | 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: October | Statement: [Tout, approximateGregorianEnd, October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateGregorianEnd Context triple: [Tout, approximateGregorianEnd, October]
-
A.
endEraInGregorianCalendar
Indicates that a particular era or historical period concludes on a specified date in the Gregorian calendar.
-
B.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
C.
hasApproxGregorianStart
Indicates that an entity has an associated start date expressed as an approximate value in the Gregorian calendar.
-
D.
endDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which the first use of something ended or ceased.
-
E.
endEraDay
Indicates the specific calendar day on which a particular era or period formally ends.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: April 29, 2026, 9:15 p.m.