Triple
T15121017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 小室眞子 |
E361170
|
entity |
| Predicate | 著名な出来事 |
P259
|
FINISHED |
| Object | 小室圭との婚約内定発表（2017年） |
—
|
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: 小室圭との婚約内定発表（2017年） | Statement: [小室眞子, 著名な出来事, 小室圭との婚約内定発表（2017年）]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 著名な出来事 Context triple: [小室眞子, 著名な出来事, 小室圭との婚約内定発表（2017年）]
-
A.
significantEvent
chosen
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
B.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
C.
notableEventPromoted
Indicates that an event was actively publicized, advertised, or otherwise promoted as notable or significant.
-
D.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
E.
hasNamesakeNotableEvent
Indicates that one entity serves as the namesake for a notable event associated with the other 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059f69a881909929a037a0eef702 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.