Triple
T24999621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Berg |
E625679
|
entity |
| Predicate | titleTransformedInto |
P25426
|
FINISHED |
| Object | Duke of Berg |
—
|
NE NERFINISHED |
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: Duke of Berg | Statement: [Count of Berg, titleTransformedInto, Duke of Berg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleTransformedInto Context triple: [Count of Berg, titleTransformedInto, Duke of Berg]
-
A.
titleBecomes
chosen
Indicates that one title changes into or is replaced by another title over time.
-
B.
titleHolderConvertedTo
Indicates that a title previously held by one entity has been transferred or converted so that it is now held in a different form or by another entity.
-
C.
titleAfterConversion
Indicates the title or designation an entity holds after undergoing a specified conversion, change, or transformation process.
-
D.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
E.
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.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 6:04 a.m.