Triple
T15793957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deep Blue |
E382927
|
entity |
| Predicate | matchStartDate |
P288
|
FINISHED |
| Object | 1997-05-03 |
—
|
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: 1997-05-03 | Statement: [Deep Blue, matchStartDate, 1997-05-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchStartDate Context triple: [Deep Blue, matchStartDate, 1997-05-03]
-
A.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
B.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
C.
originalScheduleStartDate
Indicates the date on which a schedule was initially planned or set to begin, before any later changes or adjustments.
-
D.
firstTestMatchDate
Indicates the date on which an entity (such as a team or player) participated in its first Test match.
-
E.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4db55308190875a04f982c44cea |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.