Triple
T20572524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haseki Sultan |
E505137
|
entity |
| Predicate | meaningOfComponent_haseki |
P140616
|
FINISHED |
| Object | favored |
—
|
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: favored | Statement: [Haseki Sultan, meaningOfComponent_haseki, favored]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfComponent_haseki Context triple: [Haseki Sultan, meaningOfComponent_haseki, favored]
-
A.
componentKanji2
Indicates that one kanji character serves as the second component or sub-part of another kanji.
-
B.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
C.
hasParticularSignificanceFor
Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
-
D.
hasHonden
Indicates that an entity possesses or includes a honden, typically referring to the main sanctuary building in a Shinto shrine.
-
E.
hasMeaningInJapanese
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning when interpreted in the Japanese language.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a906f0508190ac698233738f4452 |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:39 a.m.