Triple
T8710851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sene |
E206771
|
entity |
| Predicate | hasGregorianOverlap |
P70408
|
FINISHED |
| Object | June |
—
|
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: June | Statement: [Sene, hasGregorianOverlap, June]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGregorianOverlap Context triple: [Sene, hasGregorianOverlap, June]
-
A.
hasDateInGregorianCalendar
chosen
Indicates that an entity is associated with a specific date expressed using the Gregorian calendar system.
-
B.
hasHistoricalRegionOverlap
Indicates that two historical regions share a common geographic area or have partially overlapping territorial extents during a given time period.
-
C.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
D.
newYearDateGregorianLeapOverlap
Indicates that the Gregorian calendar New Year’s date coincides or overlaps with a date defined for leap-year-related observances or calculations.
-
E.
hasDateInJulianCalendar
Indicates that an entity is associated with a specific date expressed according to the Julian calendar system.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c3189f88190bb9bb77ba9d28d60 |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.