Triple
T5905296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kusanagi-no-Tsurugi |
E131327
|
entity |
| Predicate | componentOfRegalia |
P65148
|
FINISHED |
| Object | sword |
—
|
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: sword | Statement: [Kusanagi-no-Tsurugi, componentOfRegalia, sword]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentOfRegalia Context triple: [Kusanagi-no-Tsurugi, componentOfRegalia, sword]
-
A.
usesImperialRegalia
Indicates that one entity employs or incorporates imperial regalia (such as crowns, scepters, or other sovereign insignia) in relation to another entity or context.
-
B.
emblemUsedBy
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
C.
containsImperialRegalia
chosen
Indicates that one entity includes or holds the imperial regalia associated with another entity.
-
D.
isMilitaryDecorationOf
Indicates that something is a military award or honor that has been conferred upon a particular person, unit, or entity.
-
E.
crownedWith
Indicates that one entity serves as a crown, top, or decorative upper covering placed upon another 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.