Triple
T24595498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Privilegium Maius |
E608656
|
entity |
| Predicate | claimedIssuer |
P29
|
FINISHED |
| Object | Emperor Frederick I Barbarossa |
—
|
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: Emperor Frederick I Barbarossa | Statement: [Privilegium Maius, claimedIssuer, Emperor Frederick I Barbarossa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedIssuer Context triple: [Privilegium Maius, claimedIssuer, Emperor Frederick I Barbarossa]
-
A.
claimedIn
Indicates that a statement, fact, or assertion is reported or documented within a particular source, document, or claim.
-
B.
issuedBy
chosen
Indicates that something (such as a document, order, or statement) has been formally created, authorized, or released by a particular agent or authority.
-
C.
claimedExtensionBy
Indicates that one entity asserts or designates another entity as its extension, add-on, or expansion.
-
D.
issuerProduces
Indicates that an issuer creates, generates, or brings into existence a particular product, document, asset, or item.
-
E.
typicalIssuer
Indicates that one entity is the standard or commonly expected issuer (e.g., of a document, instrument, or credential) for another entity.
- 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:30 a.m.