Triple
T24695851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guardia Real |
E611581
|
entity |
| Predicate | notableLocationOfDuties |
P3858
|
FINISHED |
| Object | Palacio de la Zarzuela |
—
|
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: Palacio de la Zarzuela | Statement: [Guardia Real, notableLocationOfDuties, Palacio de la Zarzuela]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLocationOfDuties Context triple: [Guardia Real, notableLocationOfDuties, Palacio de la Zarzuela]
-
A.
notableLocation
chosen
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
B.
notableLocationUse
Indicates that a location is notably used for a particular purpose, activity, or function associated with the subject.
-
C.
notableRoleLocation
Indicates that an entity’s notable role, position, or function is specifically associated with a particular geographic location.
-
D.
notableLocationDocumented
Indicates that a specific location associated with an entity is recorded or documented as notable in some source or reference.
-
E.
notableShowLocation
Indicates that a show or performance is notably associated with, took place at, or is best known for occurring in a particular location.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 18, 2026, 3:21 a.m.