Triple
T8396001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Roman Empress |
E198052
|
entity |
| Predicate | sometimesHeldBy |
P82003
|
FINISHED |
| Object | queen consort of Germany |
—
|
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: queen consort of Germany | Statement: [Holy Roman Empress, sometimesHeldBy, queen consort of Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesHeldBy Context triple: [Holy Roman Empress, sometimesHeldBy, queen consort of Germany]
-
A.
currentlyHeldBy
Indicates that an entity is at present in the possession, control, or custody of another entity.
-
B.
laterHeldBy
Indicates that an entity was possessed, controlled, or owned by another entity at a subsequent time after an earlier state or holder.
-
C.
isUsuallyHeldBy
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
-
D.
hasHeldBy
Indicates that one entity has been physically or conceptually grasped, possessed, or kept in the control of another entity.
-
E.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
- F. None of above. chosen
Provenance (4 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb81874d6c8190bbc0ac832d8a339d |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:04 p.m.