Triple
T27399842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elisabeth, Princess of Anhalt-Zerbst |
E691801
|
entity |
| Predicate | relativeByHouse |
P26313
|
FINISHED |
| Object | Catherine the Great |
—
|
NE NERFINISHED |
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: Catherine the Great | Statement: [Elisabeth, Princess of Anhalt-Zerbst, relativeByHouse, Catherine the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeByHouse Context triple: [Elisabeth, Princess of Anhalt-Zerbst, relativeByHouse, Catherine the Great]
-
A.
relationshipBetweenHouses
Indicates a relational connection or association that exists between two or more houses.
-
B.
associatedHouse
chosen
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
C.
usedByHouse
Indicates that something is utilized or employed by a particular house.
-
D.
bondedToHouse
Indicates a relationship where an entity is legally or contractually obligated, tied, or pledged in connection to a specific house.
-
E.
relationToMLS
Indicates a relationship or association that an entity has with a specific MLS (Multiple Listing Service) system or record.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: April 27, 2026, 12:28 p.m.