Triple
T8235369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JPX-Nikkei 400 |
E192391
|
entity |
| Predicate | calculationStartDate |
P80999
|
FINISHED |
| Object | 2014-01-06 |
—
|
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: 2014-01-06 | Statement: [JPX-Nikkei 400, calculationStartDate, 2014-01-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calculationStartDate Context triple: [JPX-Nikkei 400, calculationStartDate, 2014-01-06]
-
A.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
B.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
C.
calculatedOn
Indicates that a value, result, or outcome is computed based on or using the referenced entity as its input, basis, or context.
-
D.
previewStartDate
Indicates the date and time when a preview period for something begins.
-
E.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb782931848190bcc54622f34e06a7 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb3d6c34708190a987d68529cbb0b3 |
completed | March 31, 2026, 3:20 a.m. |
Created at: March 30, 2026, 5:46 p.m.