Triple
T31311286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parmouthi |
E798467
|
entity |
| Predicate | predecessorCalendar |
P190679
|
FINISHED |
| Object | ancient Egyptian civil 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: ancient Egyptian civil calendar | Statement: [Parmouthi, predecessorCalendar, ancient Egyptian civil calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorCalendar Context triple: [Parmouthi, predecessorCalendar, ancient Egyptian civil calendar]
-
A.
predecessorHoliday
Indicates that one holiday directly precedes another in a temporal or calendrical sequence.
-
B.
predecessorStartDate
Indicates that the start date of one entity directly follows or is constrained by the start date of its predecessor entity in a sequence or dependency chain.
-
C.
predecessorEventDate
Indicates that the date specified is when an immediately preceding or prior related event occurred.
-
D.
predecessorOrganizer
Indicates that one organizer entity served in the organizing role before another organizer in a sequence of organizers.
-
E.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: April 29, 2026, 9:15 p.m.