Triple
T8710853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sene |
E206771
|
entity |
| Predicate | belongsToCalendarSystem |
P1818
|
FINISHED |
| Object | Ge'ez-based calendars |
—
|
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: Ge'ez-based calendars | Statement: [Sene, belongsToCalendarSystem, Ge'ez-based calendars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCalendarSystem Context triple: [Sene, belongsToCalendarSystem, Ge'ez-based calendars]
-
A.
belongsToCalendar
Indicates that an event or item is associated with and contained within a specific calendar.
-
B.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
C.
followsGregorianCalendar
Indicates that the entity uses or adheres to the Gregorian calendar system for dating and timekeeping.
-
D.
hasNumberOfWeekSystems
Indicates the relationship that specifies how many distinct week-based systems are associated with or used by a given entity.
-
E.
usesCalendar
chosen
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
- 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_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.