Triple
T10633405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatiana Nikolaevna of Russia |
E250514
|
entity |
| Predicate | remainsIdentified |
P47673
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tatiana Nikolaevna of Russia, remainsIdentified, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remainsIdentified Context triple: [Tatiana Nikolaevna of Russia, remainsIdentified, yes]
-
A.
remainsDiscoveredBy
Indicates that physical remains (such as fossils, artifacts, or bodies) were found or uncovered by a particular discoverer or discovering entity.
-
B.
identityRevealedIn
Indicates that an entity’s true identity becomes known or disclosed within a specified context, source, or situation.
-
C.
recognizedThrough
Indicates that something becomes known, identified, or acknowledged by means of a particular method, medium, or process.
-
D.
remainsRecoveredFrom
chosen
Indicates that physical remains of an entity have been found and retrieved from a specified source, location, or context.
-
E.
recognizedSee
Indicates that one entity sees another and consciously recognizes or identifies what is being seen.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfab47bc819086684edc1b6dce74 |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:02 p.m.