Triple
T19760150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farnborough Hill |
E474604
|
entity |
| Predicate | hasPastResident |
P130723
|
FINISHED |
| Object | royalty |
—
|
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: royalty | Statement: [Farnborough Hill, hasPastResident, royalty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPastResident Context triple: [Farnborough Hill, hasPastResident, royalty]
-
A.
hasNearbyFormerResidenceOf
Indicates that one entity is located near a place that used to be the residence of another entity.
-
B.
formerResidenceOf
Indicates that a location was once the place where a person or entity lived or was based, but is no longer their current residence.
-
C.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
-
D.
hasNotableResidentInTimeline
chosen
Indicates that an entity has, at some point in its historical timeline, a notable resident associated with it.
-
E.
hasResidences
Indicates that an entity maintains one or more places of residence at the related locations or properties.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6531f38b48190b1663870a8da5a59 |
completed | April 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.