Triple
T5219397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loyola |
E117832
|
entity |
| Predicate | notableFamilySeat |
P10501
|
FINISHED |
| Object | Loyola family home in Azpeitia |
—
|
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: Loyola family home in Azpeitia | Statement: [Loyola, notableFamilySeat, Loyola family home in Azpeitia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFamilySeat Context triple: [Loyola, notableFamilySeat, Loyola family home in Azpeitia]
-
A.
nobleFamilySeat
chosen
Indicates the location that serves as the principal seat or main residence of a noble family.
-
B.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
-
C.
associatedNobleFamily
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
D.
headOfNobleFamily
Indicates that one entity holds the position of leader or chief authority over a particular noble family.
-
E.
notableNobleFaction
Indicates that a noble is significantly associated with or belongs to a particularly prominent or influential noble faction.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7ab6e63c8190964b2b65a0206134 |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.