Triple
T34848098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Roman Emperor’s representatives |
E1004526
|
entity |
| Predicate | wereOftenDrawnFrom |
P103700
|
FINISHED |
| Object | imperial nobility |
—
|
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: imperial nobility | Statement: [Holy Roman Emperor’s representatives, wereOftenDrawnFrom, imperial nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereOftenDrawnFrom Context triple: [Holy Roman Emperor’s representatives, wereOftenDrawnFrom, imperial nobility]
-
A.
isTypicallyDrawnAt
Indicates that something is most commonly or customarily depicted or illustrated at a particular time, place, or context.
-
B.
membersDrawnFrom
chosen
Indicates that the members of one group, set, or collection are selected or sourced from another group, set, or collection.
-
C.
numberOfSurvivingDrawings
Indicates the count of drawings that still exist or remain intact from an original set.
-
D.
draws
Indicates that one entity creates a visual representation or image of another entity.
-
E.
typeOfDraw
Indicates that one entity is a specific kind or category of drawing or draw-related outcome associated with 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_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.