Triple
T8730069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nehase |
E207231
|
entity |
| Predicate | typicalGregorianStart |
P32533
|
FINISHED |
| Object | 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: August | Statement: [Nehase, typicalGregorianStart, August]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGregorianStart Context triple: [Nehase, typicalGregorianStart, August]
-
A.
typicalStartTimeOfYear
Indicates the usual or characteristic time of year when something typically begins or occurs.
-
B.
typicalStartPeriod
chosen
Indicates the usual or standard time period during which something begins or is initiated.
-
C.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
D.
followsGregorianCalendar
Indicates that the entity uses or adheres to the Gregorian calendar system for dating and timekeeping.
-
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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d26d280819085e15d4917c2b9a5 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.