Triple
T33300132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomeranian |
E852555
|
entity |
| Predicate | notableHistoricalOwner |
P128717
|
FINISHED |
| Object | Queen Victoria |
E21338
|
NE 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: Queen Victoria | Statement: [Pomeranian, notableHistoricalOwner, Queen Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHistoricalOwner Context triple: [Pomeranian, notableHistoricalOwner, Queen Victoria]
-
A.
notablePropertyOwnerOf
chosen
Indicates that a subject is a significant or noteworthy owner of a particular property or asset.
-
B.
notableHistoricalEntity
Indicates that an entity holds recognized historical significance or prominence within a historical context.
-
C.
notableHuman
Indicates that the subject is a human who is recognized as notable or significant in some context.
-
D.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
-
E.
notablePortraitSubject
Indicates that the subject is a person who is prominently or famously depicted in a portrait created by the other entity.
- F. None of above.
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_69f34966ed4c81908dc9dda82d8c7fe3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a354321e2008190a1031b3c3af87058 |
completed | June 19, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:33 a.m.