Triple
T25796080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosebery family |
E649685
|
entity |
| Predicate | hasAncestralSeatNear |
P146899
|
FINISHED |
| Object | Edinburgh |
—
|
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: Edinburgh | Statement: [Rosebery family, hasAncestralSeatNear, Edinburgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralSeatNear Context triple: [Rosebery family, hasAncestralSeatNear, Edinburgh]
-
A.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
B.
hasFamilySeatNear
chosen
Indicates that an entity’s principal family residence or ancestral seat is located in the vicinity of another specified place or entity.
-
C.
hasHistoricalSeat
Indicates that an entity possesses or is associated with a historically significant seat, location, or place of authority.
-
D.
hasAncestralLand
Indicates that an entity possesses land inherited from its ancestors or traditionally associated with its lineage.
-
E.
laterFamilySeat
Indicates that one entity serves as a subsequent or later seat, residence, or base for a particular family or lineage, following an earlier one.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 22, 2026, 6:30 a.m.