Triple
T16619897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elector of Regensburg |
E403795
|
entity |
| Predicate | hasTitleHolderCharacteristic |
P103300
|
FINISHED |
| Object | prince of the Church |
—
|
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: prince of the Church | Statement: [Elector of Regensburg, hasTitleHolderCharacteristic, prince of the Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleHolderCharacteristic Context triple: [Elector of Regensburg, hasTitleHolderCharacteristic, prince of the Church]
-
A.
hasTitleHolder
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
B.
hasTitleFeature
chosen
Indicates that an entity possesses a specific characteristic, attribute, or element related to its title.
-
C.
hasTitleHolderOrigin
Indicates that the origin or source location of a title holder is specified in relation to that title.
-
D.
hasTitleHolderResponsibility
Indicates that an entity bears the official duty or role associated with holding a particular title or position.
-
E.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754c934c8190a0a8ddd747681aa7 |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.