Triple
T36036850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Abbey of Fulda |
E1042427
|
entity |
| Predicate | hasEstateInImperialDiet |
P44656
|
FINISHED |
| Object | Bench of Prelates |
—
|
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: Bench of Prelates | Statement: [Prince-Abbey of Fulda, hasEstateInImperialDiet, Bench of Prelates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstateInImperialDiet Context triple: [Prince-Abbey of Fulda, hasEstateInImperialDiet, Bench of Prelates]
-
A.
hasPositionInImperialDiet
chosen
Indicates that an entity holds or held a formal seat or role within the Imperial Diet.
-
B.
hasBranchOfImperialFamily
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
-
C.
wasImperialDietLocation
Indicates that a place served as the location where an Imperial Diet (formal assembly of the Holy Roman Empire) was held.
-
D.
locatedInMonarchicState
Indicates that an entity is situated within the territory or jurisdiction of a state governed by a monarchy.
-
E.
hadMemberInImperialFamily
Indicates that an entity had at least one member belonging to an imperial family.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:07 p.m.