Triple
T6896718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 佳子内親王 |
E159387
|
entity |
| Predicate | メディアでの評価 |
P1782
|
FINISHED |
| Object | 親しみやすいイメージで報道されることが多い |
—
|
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: 親しみやすいイメージで報道されることが多い | Statement: [佳子内親王, メディアでの評価, 親しみやすいイメージで報道されることが多い]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: メディアでの評価 Context triple: [佳子内親王, メディアでの評価, 親しみやすいイメージで報道されることが多い]
-
A.
hasNotableCritic
Indicates that one entity serves as a significant or widely recognized critic of another entity.
-
B.
reviewOf
Indicates that one entity is a critical or evaluative assessment that is about or directed toward another entity.
-
C.
mediaCoverage
chosen
Indicates that one entity reports on, documents, or broadcasts information about another entity through news or media channels.
-
D.
mediaCovered
Indicates that one entity (such as a media outlet or source) has reported on, featured, or otherwise provided coverage of another entity or event.
-
E.
isNotedByCriticsFor
Indicates that something has been recognized and highlighted by critics specifically for a particular quality, feature, or aspect.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d95ae3f88190b7f5d440f90ae9f9 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.