Triple
T25282192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aadi Perukku |
E633850
|
entity |
| Predicate | approxGregorianDate |
P11836
|
FINISHED |
| Object | late July or early August |
—
|
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 July or early August | Statement: [Aadi Perukku, approxGregorianDate, late July or early August]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxGregorianDate Context triple: [Aadi Perukku, approxGregorianDate, late July or early August]
-
A.
dateRelativeToGregorian
chosen
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
B.
dateSecularized
Indicates the date on which a religious or ecclesiastical entity was formally converted to secular (non-religious) status.
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
calendarYearOffsetFromGregorian
Indicates the number of whole calendar years by which a given calendar system is offset relative to the Gregorian calendar.
-
E.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 1:19 p.m.