Triple
T23541174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fetternear House |
E577750
|
entity |
| Predicate | servedForCenturiesAs |
P2417
|
FINISHED |
| Object | principal seat of the Leslie family |
—
|
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: principal seat of the Leslie family | Statement: [Fetternear House, servedForCenturiesAs, principal seat of the Leslie family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedForCenturiesAs Context triple: [Fetternear House, servedForCenturiesAs, principal seat of the Leslie family]
-
A.
historicallyServedBy
Indicates that an entity was provided with services or support by another entity during a past period of time.
-
B.
centuriesOld
Indicates that something has existed or remained in existence for several hundred years.
-
C.
ownedUntilCentury
Indicates that an entity possessed or held ownership of another entity up to, but not necessarily beyond, a specified century.
-
D.
served
Indicates that one entity provided a service, assistance, or role-based function to or for another entity.
-
E.
historicallyUsedFor
chosen
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1b3a8c8190b5b6a58f0476c5d2 |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.