Triple
T6810504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izanami |
E156618
|
entity |
| Predicate | statusInYomi |
P73211
|
FINISHED |
| Object | ruler of the dead |
—
|
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: ruler of the dead | Statement: [Izanami, statusInYomi, ruler of the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInYomi Context triple: [Izanami, statusInYomi, ruler of the dead]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
statusWordRegister
Indicates the level of formality or social register associated with a status-related word in language use.
-
E.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
- 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_69c68828b26c819090fe9df7612bbc27 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30ded6481908fd64611607c610e |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:16 p.m.