Triple
T31665541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Party Foundation Day |
E808114
|
entity |
| Predicate | dateObservedInISO |
P12859
|
FINISHED |
| Object | 10-10 |
—
|
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: 10-10 | Statement: [Party Foundation Day, dateObservedInISO, 10-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateObservedInISO Context triple: [Party Foundation Day, dateObservedInISO, 10-10]
-
A.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
B.
representedInISO8601
chosen
Indicates that a temporal value or duration is expressed using the ISO 8601 standardized date and time format.
-
C.
dateNotation
Indicates how a date is written or formatted in notation (e.g., order and style of day, month, and year).
-
D.
dateVariesInGregorianCalendar
Indicates that the specific date associated with an event or entity is not fixed but changes from year to year when expressed in the Gregorian calendar.
-
E.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 30, 2026, 10:59 p.m.