Triple
T10316348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wrottesley family |
E242024
|
entity |
| Predicate | notableBranchOf |
P10432
|
FINISHED |
| Object | British nobility |
—
|
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: British nobility | Statement: [Wrottesley family, notableBranchOf, British nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBranchOf Context triple: [Wrottesley family, notableBranchOf, British nobility]
-
A.
notableBranch
chosen
Indicates that one entity is a particularly significant or prominent subdivision, offshoot, or branch of another entity.
-
B.
notableCategory
Indicates that an entity is recognized as notable or significant within a particular category or classification.
-
C.
notableCategoryType
Indicates that an entity is notably associated with or classified under a particular category type.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableHierarchy
Indicates that one entity holds a higher or more prominent rank, status, or level of importance relative to another within an ordered structure or system.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:49 a.m.