Triple
T30346253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanjiro Kamado |
E771874
|
entity |
| Predicate | notableMark |
P7734
|
FINISHED |
| Object | demon slayer mark on his forehead |
—
|
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: demon slayer mark on his forehead | Statement: [Tanjiro Kamado, notableMark, demon slayer mark on his forehead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMark Context triple: [Tanjiro Kamado, notableMark, demon slayer mark on his forehead]
-
A.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
B.
notableText
Indicates that a particular piece of text is especially significant, prominent, or worthy of attention in relation to the associated entity or context.
-
C.
notableBlock
Indicates that one entity is a block (e.g., text, code, or content segment) that is considered notable or significant in relation to another entity or context.
-
D.
notableElement
chosen
Indicates that an entity has a component, feature, or part that is especially significant, prominent, or noteworthy in relation to it.
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:56 p.m.