Triple
T15324418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Kako of Akishino |
E366372
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Kako |
E366372
|
NE 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: Kako | Statement: [Princess Kako of Akishino, givenName, Kako]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kako Context triple: [Princess Kako of Akishino, givenName, Kako]
-
A.
Kako
chosen
Kako is a member of the Japanese imperial family, known as Princess Kako of Akishino.
-
B.
Kaje
Kaje is an exonym used to refer to the Bajju people, an ethnic group primarily found in Kaduna State, Nigeria.
-
C.
Ako
Ako is a coastal city in southwestern Hyogo Prefecture, Japan, historically known for its salt production and the story of the Forty-seven Ronin.
-
D.
Koja
Koja is a coastal district in North Jakarta, Indonesia, known for its dense urban neighborhoods and proximity to the city’s port and industrial areas.
-
E.
Jakie
Jakie is a masculine given name, often used as a diminutive or variant of Jacob or Jack.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd5ce0c819093c9a14de549dff6 |
completed | April 16, 2026, 1:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef8aaef608190bd3ec9fdd215afbb |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:16 a.m.