Triple
T31612514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Imperial of Mexico |
E806663
|
entity |
| Predicate | residenceAssociatedWithTitle |
P44606
|
FINISHED |
| Object | Chapultepec 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: Chapultepec Castle | Statement: [Prince Imperial of Mexico, residenceAssociatedWithTitle, Chapultepec Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceAssociatedWithTitle Context triple: [Prince Imperial of Mexico, residenceAssociatedWithTitle, Chapultepec Castle]
-
A.
hasTitleHolderResidence
chosen
Indicates that a specified residence is the official home or dwelling place of the current holder of a particular title.
-
B.
holderResidenceBeforeTitle
Indicates that a title holder’s place of residence prior to acquiring the title is being specified.
-
C.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
-
D.
architectOfResidence
Indicates that one entity is the architect responsible for designing the residence associated with another entity.
-
E.
residenceAssociatedWithOffice
Indicates a relationship where a residence is connected or linked to a particular office, such as being located at, attached to, or officially designated for that office.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 10:37 p.m.