Triple
T33051146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Children’s Day |
E845724
|
entity |
| Predicate | hasPrimaryDate |
P203292
|
FINISHED |
| Object | 20 November |
—
|
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: 20 November | Statement: [Universal Children’s Day, hasPrimaryDate, 20 November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryDate Context triple: [Universal Children’s Day, hasPrimaryDate, 20 November]
-
A.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
B.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
C.
hasBaseDate
Indicates that an entity is associated with a specific reference or starting date used as the basis for related calculations, schedules, or validity periods.
-
D.
hasPromDate
Indicates that one entity is the person who is accompanying another entity as their date to a prom event.
-
E.
hasPrimaryMeeting
Indicates that an entity is associated with its main or most important meeting, distinguishing it from other meetings it may have.
- F. None of above. chosen
Provenance (4 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a014a0b57dc8190b04ce51156ab95fa |
completed | May 11, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_6a0149afa57c8190a83257085766d916 |
completed | May 11, 2026, 3:14 a.m. |
| PDg | Predicate description generation | batch_6a014a0ab56c819082ce383fb5987654 |
completed | May 11, 2026, 3:16 a.m. |
Created at: May 1, 2026, 1:24 a.m.