Triple
T38662387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Day Preparatory Committee |
E940366
|
entity |
| Predicate | eventDateManaged |
P140492
|
FINISHED |
| Object | 10 October (Double Ten Day) |
—
|
NE NERFINISHED |
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 October (Double Ten Day) | Statement: [National Day Preparatory Committee, eventDateManaged, 10 October (Double Ten Day)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDateManaged Context triple: [National Day Preparatory Committee, eventDateManaged, 10 October (Double Ten Day)]
-
A.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
B.
mainEventDate
chosen
Indicates the primary or most significant date on which the referenced event occurs or is scheduled to occur.
-
C.
eventStartDateOrganized
Indicates the date on which an event is formally scheduled or organized to begin.
-
D.
eventDateReviewed
Indicates the date on which an event was examined, checked, or formally reviewed.
-
E.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.