Triple
T36999682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiro Lolita |
E915315
|
entity |
| Predicate | usesAccessoryType |
P74466
|
FINISHED |
| Object | white headbows |
—
|
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: white headbows | Statement: [Shiro Lolita, usesAccessoryType, white headbows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAccessoryType Context triple: [Shiro Lolita, usesAccessoryType, white headbows]
-
A.
hasAccessoryType
chosen
Indicates that an entity is associated with or characterized by a particular type or category of accessory.
-
B.
accessory
Indicates that one entity serves as a supplementary or supporting item to another, often enhancing its function, use, or appearance.
-
C.
hasAccessoryEcosystem
Indicates that an entity is associated with a surrounding set of compatible accessories, add-ons, or peripheral products designed to work with it.
-
D.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
E.
isAccessoryFruit
Indicates that a fruit develops from tissues other than (or in addition to) the ovary, such as the receptacle or floral parts, rather than solely from the ovary itself.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.