Triple
T196687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taisho era |
E3831
|
entity |
| Predicate | massMediaForm |
P131
|
FINISHED |
| Object | newspapers |
—
|
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: newspapers | Statement: [Taisho era, massMediaForm, newspapers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massMediaForm Context triple: [Taisho era, massMediaForm, newspapers]
-
A.
mediaType
chosen
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
B.
fareMedia
Indicates that a particular type of ticket, pass, or payment instrument is used as the medium for paying a fare.
-
C.
mediaCoverage
Indicates that one entity reports on, documents, or broadcasts information about another entity through news or media channels.
-
D.
mediaMarket
Indicates a relationship where a media outlet or content provider serves, targets, or operates within a particular geographic or demographic market.
-
E.
broadcastNetwork
Indicates that one entity serves as the television or radio network that broadcasts the programming or content 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a2598594388190a56f36fa036eac84 |
completed | Feb. 28, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69a25677da14819094cd02868fd30c83 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.