Triple
T11876962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | うめだスカイビル |
E282551
|
entity |
| Predicate | メディア露出 |
P37618
|
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.
mediaExposure
chosen
Indicates the extent to which an entity is subjected to or receives attention from media channels such as television, radio, print, or online platforms.
-
B.
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.
-
C.
mediaCoverage
Indicates that one entity reports on, documents, or broadcasts information about another entity through news or media channels.
-
D.
socialMediaAppearance
Indicates that an entity is featured, mentioned, or otherwise present in a piece of content on a social media platform.
-
E.
mediaCoverageAs
Indicates that one entity provides or receives media coverage in the role, capacity, or format specified by 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.