Triple
T15488230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Holstein-Gottorp |
E377106
|
entity |
| Predicate | hasHolderCharacteristic |
P118427
|
FINISHED |
| Object | member of ruling elite |
—
|
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: member of ruling elite | Statement: [Duchess of Holstein-Gottorp, hasHolderCharacteristic, member of ruling elite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHolderCharacteristic Context triple: [Duchess of Holstein-Gottorp, hasHolderCharacteristic, member of ruling elite]
-
A.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
B.
hasHolding
Indicates that one entity possesses, controls, or maintains ownership or custody of another entity as an asset or item.
-
C.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
-
D.
hasHeldBy
Indicates that one entity has been physically or conceptually grasped, possessed, or kept in the control of another entity.
-
E.
hasPocketType
Indicates the specific style or configuration of pocket associated with an item or garment.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03faaca588190b0397bc2e27a522a |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:48 a.m.