Triple
T14723830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Prussia (by marriage) |
E345883
|
entity |
| Predicate | notAcquiredBy |
P57337
|
FINISHED |
| Object | 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: birth | Statement: [Princess of Prussia (by marriage), notAcquiredBy, birth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAcquiredBy Context triple: [Princess of Prussia (by marriage), notAcquiredBy, birth]
-
A.
notHeldIn
Indicates that an event, activity, or state does not take place or is not located within a specified context, location, or time frame.
-
B.
notAvailableFor
Indicates that an entity is currently not accessible, usable, or eligible for a particular action, purpose, or association.
-
C.
notAutomaticallyHeldBy
chosen
Indicates that a particular right, status, or condition is not granted or possessed by default and must be explicitly obtained or established.
-
D.
notUsedAt
Indicates that a particular entity is not utilized, applied, or active at a specified location, time, or context.
-
E.
doesNotHave
Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec25e9a14819081fa06fc601f295d |
completed | April 14, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.