Triple
T25942945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Henry of Battenberg |
E653755
|
entity |
| Predicate | titleUsedFromMarriage |
P77742
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Princess Henry of Battenberg, titleUsedFromMarriage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleUsedFromMarriage Context triple: [Princess Henry of Battenberg, titleUsedFromMarriage, true]
-
A.
usedMarriageFor
Indicates that one party employed marriage as a means or tool to achieve some goal, benefit, or ulterior purpose involving another party.
-
B.
hasMarriedSurname
Indicates that a person’s current surname is the one they adopted through marriage.
-
C.
usedDuringMarriageTo
Indicates that something (such as a name, asset, or status) was in use by or applicable to a person or entity specifically during the period of their marriage.
-
D.
laterMarriedName
Indicates that the referenced name is a surname or full name a person adopted after a later marriage, replacing or succeeding their previous name.
-
E.
titleFromSpouse
chosen
Indicates that an entity holds a title or honorific that is derived from or acquired through their spouse.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 22, 2026, 8:41 a.m.