Triple
T28826162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Denham |
E727909
|
entity |
| Predicate | treatsAsRivals |
P100279
|
FINISHED |
| Object | her potential heirs |
—
|
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: her potential heirs | Statement: [Lady Denham, treatsAsRivals, her potential heirs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsAsRivals Context triple: [Lady Denham, treatsAsRivals, her potential heirs]
-
A.
rivalryCharacterizedBy
Indicates a relationship where a rivalry is defined or distinguished by a particular feature, quality, or circumstance.
-
B.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
C.
rivalOf
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
D.
involvesRivalryBetween
chosen
Indicates a relationship in which two or more entities are engaged in rivalry or competitive opposition with one another.
-
E.
rivalryLevel
Indicates the degree or intensity of competitive opposition or conflict between two entities.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 6:36 a.m.