Triple
T29860999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnett of Leys family |
E758314
|
entity |
| Predicate | seatManagedBy |
P167677
|
FINISHED |
| Object | National Trust for Scotland |
—
|
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: National Trust for Scotland | Statement: [Burnett of Leys family, seatManagedBy, National Trust for Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatManagedBy Context triple: [Burnett of Leys family, seatManagedBy, National Trust for Scotland]
-
A.
seatGrantedBy
Indicates that a position, seat, or place (e.g., in a body or venue) is conferred or allocated to someone or something by a specific granting authority or entity.
-
B.
seatOwnedBy
Indicates that a particular seat is possessed or held in ownership by a specific entity.
-
C.
seatDesignatedBy
Indicates that a specific seat has been assigned or allocated to an entity by a particular agent or authority.
-
D.
bookingManagedBy
Indicates that the responsibility for handling, organizing, or overseeing a booking lies with a specific managing party or system.
-
E.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with another entity.
- F. None of above. chosen
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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67685c8c0819089a31631bfba0797 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66bd123108190b451eb6e23842adb |
completed | May 2, 2026, 9:25 p.m. |
Created at: April 29, 2026, 5:49 p.m.