Triple
T1288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oN-Line System |
E25
|
entity |
| Predicate | demonstrationDate |
P284
|
FINISHED |
| Object | 1968-12-09 |
—
|
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: 1968-12-09 | Statement: [oN-Line System, demonstrationDate, 1968-12-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demonstrationDate Context triple: [oN-Line System, demonstrationDate, 1968-12-09]
-
A.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
B.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
C.
dateOfSubmission
Indicates the specific date on which something (such as a document, application, or assignment) was formally submitted.
-
D.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
E.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
- 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_69a22a285828819081a58308fb963df1 |
completed | Feb. 27, 2026, 11:35 p.m. |
| NER | Named-entity recognition | batch_69a23344daf8819083118bbac5f46568 |
completed | Feb. 28, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69a232e52e7c81909c072703e28e8c61 |
completed | Feb. 28, 2026, 12:12 a.m. |
| PDg | Predicate description generation | batch_69a233443224819097b91b150fdfbd1a |
completed | Feb. 28, 2026, 12:13 a.m. |
Created at: Feb. 27, 2026, 11:36 p.m.