Triple
T29861136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fraser family |
E758317
|
entity |
| Predicate | hasFamilySeatType |
P1912
|
FINISHED |
| Object | castle |
—
|
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: castle | Statement: [Fraser family, hasFamilySeatType, castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilySeatType Context triple: [Fraser family, hasFamilySeatType, castle]
-
A.
hasFamilySeatNear
Indicates that an entity’s principal family residence or ancestral seat is located in the vicinity of another specified place or entity.
-
B.
hasFamilySeatSinceCentury
Indicates that an entity has held its principal family residence or ancestral seat continuously since a specified century.
-
C.
hasFamilyRide
Indicates that an entity offers or is associated with a ride or attraction designed to be suitable and enjoyable for families.
-
D.
hasPrioritySeating
Indicates that one entity provides or designates reserved or preferential seating for another entity.
-
E.
familySeat
chosen
Indicates the traditional principal residence or ancestral home associated with a particular family or lineage.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 29, 2026, 5:49 p.m.