Triple
T4714476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kindai University |
E104598
|
entity |
| Predicate | nameChangeEffectiveDate |
P801
|
FINISHED |
| Object | 2016-04-01 |
—
|
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-04-01 | Statement: [Kindai University, nameChangeEffectiveDate, 2016-04-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameChangeEffectiveDate Context triple: [Kindai University, nameChangeEffectiveDate, 2016-04-01]
-
A.
nameChangeDate
chosen
Indicates the date on which an entity’s name was officially changed.
-
B.
brandingChangeDate
Indicates the date on which a change in branding (such as name, logo, or visual identity) took effect.
-
C.
nameChangeApprovedBy
Indicates that an official approval has been granted by a specific authority or party for a change of name.
-
D.
startDateChangedTo
Indicates that the start date of something has been modified from its previous value to a new specified date.
-
E.
dateChangesWith
Indicates that the date associated with one entity is altered or updated in conjunction with, or as a result of, a change involving 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.