Triple
T36592867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O Oriens |
E902715
|
entity |
| Predicate | dateTraditionallySung |
P31438
|
FINISHED |
| Object | December 21 |
—
|
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: December 21 | Statement: [O Oriens, dateTraditionallySung, December 21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateTraditionallySung Context triple: [O Oriens, dateTraditionallySung, December 21]
-
A.
traditionallyDated
chosen
Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
-
B.
traditionallySungAfter
Indicates that one song or musical piece is customarily performed immediately following another in a cultural or traditional sequence.
-
C.
calendarTradition
Indicates a relationship where a calendar is based on, follows, or embodies a particular cultural, religious, or historical tradition.
-
D.
numberTradition
Indicates a relationship where a specific number is associated with, or holds significance within, a particular tradition or customary practice.
-
E.
traditionalDateInJapan
Indicates that an entity has a specific date expressed in the traditional Japanese calendar system (e.g., era-based or lunisolar date).
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.