Triple
T32924898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Núr |
E842239
|
entity |
| Predicate | belongsToCalendarStructure |
P27704
|
FINISHED |
| Object | 19-month structure |
—
|
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: 19-month structure | Statement: [Núr, belongsToCalendarStructure, 19-month structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCalendarStructure Context triple: [Núr, belongsToCalendarStructure, 19-month structure]
-
A.
belongsToCalendar
chosen
Indicates that an event or item is associated with and contained within a specific calendar.
-
B.
hasCalendarAssociation
Indicates that there is a defined relationship or linkage between an entity and a calendar or calendar-related item (such as an event, schedule, or time period).
-
C.
hasCalendarStructure
Indicates that something possesses or follows a specific calendar-based organizational structure (e.g., dates, months, or scheduling framework).
-
D.
calendarTypeLinked
Indicates that one calendar type is associated or connected to another, typically implying a defined relationship or dependency between the two calendar systems.
-
E.
followsCalendarOf
Indicates that one entity adopts and adheres to the scheduling, events, or time structure defined by another entity’s calendar.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: May 1, 2026, 1:20 a.m.