Triple
T27542360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rashō Gate |
E695268
|
entity |
| Predicate | hasNotableThemeInDepictions |
P7671
|
FINISHED |
| Object | poverty |
—
|
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: poverty | Statement: [Rashō Gate, hasNotableThemeInDepictions, poverty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableThemeInDepictions Context triple: [Rashō Gate, hasNotableThemeInDepictions, poverty]
-
A.
notableTheme
chosen
Indicates that a particular theme is prominently featured in, or strongly associated with, an entity such as a work, event, or body of content.
-
B.
hasNotableWorkDepiction
Indicates that an entity has a notable work in which it is depicted or represented.
-
C.
notableForDepicting
Indicates that something is recognized or distinguished specifically for portraying or representing a particular subject, theme, or scene.
-
D.
hasNotableIllustrationsOf
Indicates that something contains or features particularly significant or noteworthy illustrations depicting another entity or subject.
-
E.
hasCulturalDepiction
Indicates that one entity is represented, portrayed, or depicted in the cultural work or expression of 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: April 27, 2026, 1:31 p.m.