Triple
T36143169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Rutland |
E1045369
|
entity |
| Predicate | nobleFamilySeatAssociated |
P10501
|
FINISHED |
| Object | Belvoir Castle |
—
|
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: Belvoir Castle | Statement: [Earl of Rutland, nobleFamilySeatAssociated, Belvoir Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleFamilySeatAssociated Context triple: [Earl of Rutland, nobleFamilySeatAssociated, Belvoir Castle]
-
A.
nobleFamilySeat
chosen
Indicates the location that serves as the principal seat or main residence of a noble family.
-
B.
associatedNobleFamily
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
C.
formerFamilySeat
Indicates that a location was previously the principal residence or ancestral home of a particular family but no longer holds that status.
-
D.
usedByNobleFamily
Indicates that something is employed, possessed, or otherwise utilized by a noble family.
-
E.
headOfNobleFamily
Indicates that one entity holds the position of leader or chief authority over a particular noble family.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.