Triple
T17389886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Prussia |
E422789
|
entity |
| Predicate | birthConferment |
P127301
|
FINISHED |
| Object | title could be acquired by birth |
—
|
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: title could be acquired by birth | Statement: [Princess of Prussia, birthConferment, title could be acquired by birth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthConferment Context triple: [Princess of Prussia, birthConferment, title could be acquired by birth]
-
A.
coronatedNameAtBirth
Indicates that an entity’s coronation name is the same as their name at birth.
-
B.
gaveBirthTo
Indicates that one entity is the biological parent who delivered another entity as offspring.
-
C.
monarchDuringBirth
Indicates that one entity was the reigning monarch at the time another entity was born.
-
D.
birthEmpire
Indicates that an entity was born within the territory or jurisdiction of a specified empire.
-
E.
birthAnnouncedBy
Indicates that an entity’s birth is publicly communicated or reported by another entity.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a8c718c81909cb20749aaf12897 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.