Triple
T34848094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Roman Emperor’s representatives |
E1004526
|
entity |
| Predicate | couldHoldTitle |
P115009
|
FINISHED |
| Object | plenipotentiary |
—
|
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: plenipotentiary | Statement: [Holy Roman Emperor’s representatives, couldHoldTitle, plenipotentiary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldHoldTitle Context triple: [Holy Roman Emperor’s representatives, couldHoldTitle, plenipotentiary]
-
A.
mayHoldTitleOf
Indicates that an entity is permitted or eligible to possess or bear a particular title.
-
B.
heldTitleUnder
Indicates that one entity possessed or occupied a particular title, rank, or office under the authority, jurisdiction, or auspices of another entity.
-
C.
heldTitleWithin
Indicates that an entity held a specific title, position, or rank within a particular organization, jurisdiction, or domain.
-
D.
titleHolderCouldBe
chosen
Indicates that a particular entity is a possible or potential holder of a specified title or position.
-
E.
titleHeldTo
Indicates that one entity holds or possesses a specific title in relation to 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.