Triple
T3320477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grosvenor family |
E69781
|
entity |
| Predicate | hasEarlierTitleCreationDate |
P5873
|
FINISHED |
| Object | Marquessate of Westminster created in 1831 |
—
|
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: Marquessate of Westminster created in 1831 | Statement: [Grosvenor family, hasEarlierTitleCreationDate, Marquessate of Westminster created in 1831]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlierTitleCreationDate Context triple: [Grosvenor family, hasEarlierTitleCreationDate, Marquessate of Westminster created in 1831]
-
A.
hasLaterTitle
Indicates that one title occurs chronologically after another title in a sequence or timeline.
-
B.
hasTitleCreatedIn
Indicates that a title held by an entity was created or established in a specific time or period.
-
C.
createdBefore
chosen
Indicates that one entity was created at an earlier time than another entity.
-
D.
replacedEarlierTitle
Indicates that one title or designation has been superseded by an earlier title that it replaced in a sequence of naming or labeling.
-
E.
usedAsTitleBeforeName
Indicates that a term or phrase functions as a formal title placed immediately before a person's name.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13a4e948190841134d6ae6ef432 |
completed | March 8, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.