Triple
T14348066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Hohenzollern |
E355778
|
entity |
| Predicate | hasMediatizedStatus |
P113885
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Prince of Hohenzollern, hasMediatizedStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMediatizedStatus Context triple: [Prince of Hohenzollern, hasMediatizedStatus, true]
-
A.
hasStatusInMedia
Indicates that an entity is portrayed with a particular status or condition within a specific media work or context.
-
B.
couldBeMediatizedBy
Indicates that one entity has the potential to be transformed, represented, or conveyed through media by another entity.
-
C.
hasCommonMedia
Indicates that two entities share at least one media item (such as an image, video, or audio file) in common.
-
D.
mediatisedBy
Indicates that an entity’s communication or interaction is conveyed, shaped, or influenced through a particular medium or media channel rather than occurring directly.
-
E.
hasAssociatedMedium
Indicates that one entity is linked to another entity that serves as its medium, format, or channel of expression or transmission.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e8d081c8190ac805726a3e98f4c |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e8a40e4819080240c874da1842c |
completed | April 14, 2026, 12:09 p.m. |
Created at: April 10, 2026, 1:14 a.m.