Triple
T2276374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sigd |
E50779
|
entity |
| Predicate | approximateGregorianTiming |
P11836
|
FINISHED |
| Object | late October or November |
—
|
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: late October or November | Statement: [Sigd, approximateGregorianTiming, late October or November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateGregorianTiming Context triple: [Sigd, approximateGregorianTiming, late October or November]
-
A.
dateRelativeToGregorian
chosen
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
B.
positionInGregorianCalendar
Indicates the specific placement or ordering of a time-related entity within the structure of the Gregorian calendar.
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
E.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
- 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1ecc600819095dd4f69af1d18d8 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.