Triple
T31878343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dowager Duchess |
E813804
|
entity |
| Predicate | mayBeSupersededInPrecedenceBy |
P180901
|
FINISHED |
| Object | current duchess consort |
—
|
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: current duchess consort | Statement: [Dowager Duchess, mayBeSupersededInPrecedenceBy, current duchess consort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeSupersededInPrecedenceBy Context triple: [Dowager Duchess, mayBeSupersededInPrecedenceBy, current duchess consort]
-
A.
supersededInPrecisionBy
Indicates that one entity’s level of precision has been replaced or overtaken by another entity’s greater precision.
-
B.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
C.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
D.
isSuccessorTo
Indicates that one entity directly follows another in an ordered sequence, coming immediately after it.
-
E.
usedByPredecessorOf
Indicates that something is used by an entity that is the predecessor of another entity in a sequence or hierarchy.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_69f75788d40c819083bf2567b3091585 |
completed | May 3, 2026, 2:11 p.m. |
Created at: April 30, 2026, 11:55 p.m.