Triple
T14262844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DS512 |
E353567
|
entity |
| Predicate | requestForConsultationsDate |
P65519
|
FINISHED |
| Object | 2016-09-14 |
—
|
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: 2016-09-14 | Statement: [DS512, requestForConsultationsDate, 2016-09-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestForConsultationsDate Context triple: [DS512, requestForConsultationsDate, 2016-09-14]
-
A.
recommendedDate
chosen
Indicates the date on which something is advised or suggested to occur, be used, or be acted upon.
-
B.
requiresConsultationWith
Indicates that performing an action or making a decision depends on first obtaining input, approval, or advice from a specified party.
-
C.
appointmentType
Indicates the specific category or nature of an appointment associated with an entity or event.
-
D.
reasonForAppointment
Indicates the underlying purpose or cause for which an appointment is scheduled or taking place.
-
E.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de63563fc88190b0abdbf8529c65eb |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:09 a.m.