Triple
T32066748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kairi |
E818900
|
entity |
| Predicate | hasNobody |
P203004
|
FINISHED |
| Object | Naminé |
—
|
NE NERFINISHED |
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: Naminé | Statement: [Kairi, hasNobody, Naminé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobody Context triple: [Kairi, hasNobody, Naminé]
-
A.
hadNo
Indicates that one entity completely lacked or did not possess another entity, attribute, or relationship.
-
B.
roleInNobody
Indicates that an entity has a specific role or function within the context of the work titled "Nobody" (e.g., a film, book, or other creative work named "Nobody").
-
C.
hasNotableCelebrant
Indicates that an entity (such as an event, holiday, or occasion) is associated with a specific person or group who is prominently recognized for celebrating or observing it.
-
D.
hasNoPersonalNameIn
Indicates that an entity lacks a specific personal name within a given context, language, or naming system.
-
E.
hasNotableAuthorityFigure
Indicates that an entity is associated with a prominent individual who holds significant authority or leadership over it.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00d9717a9881908194163d719f14d6 |
completed | May 10, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a00d91db2ec81909ebacfc9f0d11dd8 |
completed | May 10, 2026, 7:14 p.m. |
| PDg | Predicate description generation | batch_6a00d970a11081908f24876a0696d827 |
completed | May 10, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:22 a.m.