Triple
T11852071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President Roxas |
E281930
|
entity |
| Predicate | usesDateFormat |
P44879
|
FINISHED |
| Object | month-day-year |
—
|
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: month-day-year | Statement: [President Roxas, usesDateFormat, month-day-year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDateFormat Context triple: [President Roxas, usesDateFormat, month-day-year]
-
A.
dateFormat
Indicates the specific pattern or structure used to represent a date as a formatted string.
-
B.
dateNotation
chosen
Indicates how a date is written or formatted in notation (e.g., order and style of day, month, and year).
-
C.
dateFormedFrom
Indicates that one date value is derived or constructed from another date or date-related source.
-
D.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
E.
usesUTCOffset
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a696ee548190800d56c64c339b10 |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.