Triple
T1459914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | November |
E31486
|
entity |
| Predicate | positionInRomanCalendar |
P29015
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [November, positionInRomanCalendar, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRomanCalendar Context triple: [November, positionInRomanCalendar, 9]
-
A.
positionInHebrewCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Hebrew calendar.
-
B.
positionInIslamicCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Islamic (Hijri) calendar.
-
C.
dateInRomanCatholicChurch
Indicates that a specific date is recognized, observed, or used within the context of the Roman Catholic Church’s liturgical or ecclesiastical calendar.
-
D.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
E.
positionInEra
Indicates the temporal placement or role of something within a specific historical or chronological era.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59d6dd88190b8ff3bda90aef7e2 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52bbb748190aaa804438d31f4c2 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8 p.m.