Triple
T11038079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order No. 1 |
E260937
|
entity |
| Predicate | dateIssuedOldStyle |
P23455
|
FINISHED |
| Object | 1917-02-28 |
—
|
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: 1917-02-28 | Statement: [Order No. 1, dateIssuedOldStyle, 1917-02-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateIssuedOldStyle Context triple: [Order No. 1, dateIssuedOldStyle, 1917-02-28]
-
A.
dateOldStyle
chosen
Indicates that a given date is expressed using the Old Style (Julian calendar) rather than the New Style (Gregorian calendar) convention.
-
B.
birthDateOldStyle
Indicates that an entity’s birth date is recorded according to an older or superseded calendar or dating system (e.g., Julian vs. Gregorian).
-
C.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
dateNotation
Indicates how a date is written or formatted in notation (e.g., order and style of day, month, and year).
-
E.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797fd5fe081908af13835b18de7b8 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.