Triple
T21201426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoroastrian priesthood |
E522462
|
entity |
| Predicate | performsCalendarFunction |
P96907
|
FINISHED |
| Object | maintenance of Zoroastrian calendar |
—
|
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: maintenance of Zoroastrian calendar | Statement: [Zoroastrian priesthood, performsCalendarFunction, maintenance of Zoroastrian calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsCalendarFunction Context triple: [Zoroastrian priesthood, performsCalendarFunction, maintenance of Zoroastrian calendar]
-
A.
hasCalendarFunction
Indicates that an entity possesses or supports a calendar-related capability or functionality.
-
B.
performsFunctionAt
Indicates that an entity carries out or executes a specific function at a particular location, time, or contextual point.
-
C.
performedFunction
Indicates that an entity has carried out or executed a particular function, role, or operation.
-
D.
hasFunctionInCalendar
chosen
Indicates that something serves a specific role or performs a particular function within a calendar system or scheduling context.
-
E.
calendarFunction
Indicates a relationship where an entity serves as a function or operation within a calendar system, such as computing or manipulating dates, times, or calendar-related 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73431973c81908c8682d7808a9d13 |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:18 p.m.