Triple
T35291581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Dalrymple, 1st Earl of Stair |
E1019240
|
entity |
| Predicate | associated place |
P112751
|
FINISHED |
| Object | Stair, Ayrshire |
E601004
|
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: Stair, Ayrshire | Statement: [John Dalrymple, 1st Earl of Stair, associated place, Stair, Ayrshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associated place Context triple: [John Dalrymple, 1st Earl of Stair, associated place, Stair, Ayrshire]
-
A.
relatedPlace
Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
-
B.
personAssociatedPlace
chosen
Indicates that a person has a notable connection or association with a particular place, such as residence, origin, work, or frequent presence.
-
C.
targetedPlace
Indicates that an entity intentionally directed an action, operation, or influence toward a specific place or location.
-
D.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
E.
historicallyLinkedPlace
Indicates that one place has a significant historical connection or association with another place.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
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_6a3819e150648190877afa433023cebc |
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.