Triple
T29905812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa de San Felipe de Austria |
E759530
|
entity |
| Predicate | namedForRoyalHouse |
P90174
|
FINISHED |
| Object | House of Habsburg |
—
|
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: House of Habsburg | Statement: [Villa de San Felipe de Austria, namedForRoyalHouse, House of Habsburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForRoyalHouse Context triple: [Villa de San Felipe de Austria, namedForRoyalHouse, House of Habsburg]
-
A.
namedForMonarch
chosen
Indicates that one entity bears a name derived from or given in honor of a monarch.
-
B.
royalHouseNameForm
Indicates the specific linguistic or formal version of a royal house’s name used in a given context.
-
C.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
D.
notableRoyalHouse
Indicates that an entity is prominently associated with, or belongs to, a particular royal house or dynasty.
-
E.
hasRoyalHousehold
Indicates that an entity possesses or is associated with a specific royal household as its official domestic or courtly establishment.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 29, 2026, 6:08 p.m.