Triple
T31810400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Enchancia |
E811987
|
entity |
| Predicate | princess |
P75321
|
FINISHED |
| Object | Princess Sofia |
—
|
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: Princess Sofia | Statement: [Kingdom of Enchancia, princess, Princess Sofia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: princess Context triple: [Kingdom of Enchancia, princess, Princess Sofia]
-
A.
princessOf
chosen
Indicates that one entity holds the royal title or role of princess in relation to another entity, typically a realm, family, or sovereign.
-
B.
ממלכה
Indicates a relationship where an entity functions as or belongs to a kingdom, typically denoting political or territorial sovereignty under a monarch.
-
C.
featuresPrincess
Indicates that something includes or prominently presents a princess as a central element or character.
-
D.
royalMistressOf
Indicates that one person is the (typically unofficial) romantic or sexual partner of a royal figure, such as a king or prince.
-
E.
notableCrownPrincess
Indicates that the person holds or held the title of crown princess and is distinguished or noteworthy in that role.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:43 p.m.