Triple
T30264121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelers’ Palace |
E769586
|
entity |
| Predicate | hasEmpressResident |
P122008
|
FINISHED |
| Object | Catherine II of Russia |
—
|
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 II of Russia | Statement: [Travelers’ Palace, hasEmpressResident, Catherine II of Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmpressResident Context triple: [Travelers’ Palace, hasEmpressResident, Catherine II of Russia]
-
A.
lastEmperorResident
Indicates that the subject is the final emperor who resided in, or was based at, the object location.
-
B.
associatedEmpress
chosen
Indicates a relationship where an empress is linked or connected to another entity, such as a person, place, event, or object, in a relevant or context-specific way.
-
C.
hasEmperorPresent
Indicates that an emperor is currently present at or attending a given place, event, or context.
-
D.
hasImperialPalace
Indicates that an entity possesses or is the location of an official imperial palace.
-
E.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:42 p.m.