Triple
T29585430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amshir |
E753705
|
entity |
| Predicate | calendarEraAlignment |
P167477
|
FINISHED |
| Object | Gregorian calendar |
—
|
NE NERFINISHED |
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: Gregorian calendar | Statement: [Amshir, calendarEraAlignment, Gregorian calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarEraAlignment Context triple: [Amshir, calendarEraAlignment, Gregorian calendar]
-
A.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
B.
recurringEra
Indicates a relationship where a particular era or time period repeats or recurs, rather than occurring only once.
-
C.
positionInEra
Indicates the temporal placement or role of something within a specific historical or chronological era.
-
D.
prefersEra
Indicates a relationship where one entity favors or is more inclined toward a particular historical or cultural era over others.
-
E.
representsEra
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
- F. None of above. chosen
Provenance (4 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d7d3ac48190adef6aa96f5a5b45 |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:10 p.m.