Triple
T38484098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home family |
E917865
|
entity |
| Predicate | laterTitleIn |
P17035
|
FINISHED |
| Object | Peerage of the United Kingdom |
—
|
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: Peerage of the United Kingdom | Statement: [Home family, laterTitleIn, Peerage of the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTitleIn Context triple: [Home family, laterTitleIn, Peerage of the United Kingdom]
-
A.
laterTitleHolder
Indicates that one entity is a subsequent holder of a particular title or position previously held by another entity.
-
B.
titleLaterStyledAs
Indicates that an entity held a particular title that was subsequently changed or restyled to a different form at a later time.
-
C.
hasLaterTitle
chosen
Indicates that one title occurs chronologically after another title in a sequence or timeline.
-
D.
laterTitleUsage
Indicates that a title is used or applied to an entity at a later time or in a subsequent context relative to an earlier title usage.
-
E.
languageOfLaterTitle
Indicates that the specified language is the language in which a later or subsequent title of an entity is expressed.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a017590e01c8190b985bb50cc6cd605 |
completed | May 11, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_6a0175406b348190a5809b5f3497d46f |
completed | May 11, 2026, 6:20 a.m. |
Created at: May 3, 2026, 4:31 p.m.