Triple
T35303303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glazebrook House, Gloucester, England |
E1019563
|
entity |
| Predicate | notableResidentBirth |
P12823
|
FINISHED |
| Object | Herbert Vaughan |
E946240
|
NE 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: Herbert Vaughan | Statement: [Glazebrook House, Gloucester, England, notableResidentBirth, Herbert Vaughan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableResidentBirth Context triple: [Glazebrook House, Gloucester, England, notableResidentBirth, Herbert Vaughan]
-
A.
birthDateOfNotableResident
Indicates the date of birth of a person who is a notable or distinguished resident of a given place.
-
B.
notableBirth
Indicates that one entity is the place or context in which another entity was born, highlighting a notable birth event.
-
C.
notablyBornBy
Indicates that an entity’s birth is notably attributed to, or significantly associated with, a particular parent or progenitor.
-
D.
hasNotablePersonBornHere
chosen
Indicates that a notable or distinguished person was born at the referenced place.
-
E.
notableHuman
Indicates that the subject is a human who is recognized as notable or significant in some context.
- F. None of above.
Provenance (4 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819ebd09c8190b241138004dd6f7c |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.