Triple
T29750182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waldeck region |
E752870
|
entity |
| Predicate | wasMediatized |
P156328
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Waldeck region, wasMediatized, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMediatized Context triple: [Waldeck region, wasMediatized, no]
-
A.
mediatisedTo
chosen
Indicates that one entity has been placed under the indirect rule, protection, or authority of another, typically losing direct sovereignty while remaining formally distinct.
-
B.
couldBeMediatizedBy
Indicates that one entity has the potential to be transformed, represented, or conveyed through media by another entity.
-
C.
hasRepresentationInMedia
Indicates that something is depicted, portrayed, or otherwise represented within a particular medium or media work.
-
D.
isPopularInMedia
Indicates that an entity is frequently featured, referenced, or well-liked across various media channels or platforms.
-
E.
hasMediaCoverageSince
Indicates that an entity has had media coverage starting from a specified point in time and continuing from then onward.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6736a13f08190b9695bb8796e0aec |
completed | May 2, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:53 p.m.