Triple
T21256031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Reuss |
E523870
|
entity |
| Predicate | titleContinuesAs |
P143400
|
FINISHED |
| Object | mediatized princely title |
—
|
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: mediatized princely title | Statement: [Prince of Reuss, titleContinuesAs, mediatized princely title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleContinuesAs Context triple: [Prince of Reuss, titleContinuesAs, mediatized princely title]
-
A.
titleContinuity
Indicates that two works share a continuous or consistent use of the same title across versions, installments, or related contexts.
-
B.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
C.
titleStart
Indicates that one entity’s title begins with the text or substring represented by the other entity.
-
D.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
E.
titleRetainedAfter
Indicates that an entity continues to hold or use the same title after a specified event or point in time.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735a1f9e08190b494f582bcae5c35 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:58 p.m.