Triple
T2415726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guadalupe Victoria |
E52296
|
entity |
| Predicate | adoptedNameReason |
P7885
|
FINISHED |
| Object | in honor of Our Lady of Guadalupe |
—
|
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: in honor of Our Lady of Guadalupe | Statement: [Guadalupe Victoria, adoptedNameReason, in honor of Our Lady of Guadalupe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedNameReason Context triple: [Guadalupe Victoria, adoptedNameReason, in honor of Our Lady of Guadalupe]
-
A.
reasonForName
chosen
Indicates the explanation or cause behind why an entity has a particular name.
-
B.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
-
C.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
-
D.
currentNameAdoptedBy
Indicates that an entity has adopted or started using a particular current name.
-
E.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc94d048481908409d60129aef747 |
completed | March 7, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69abc5a6cbd0819086c0716e266b7ebb |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:41 p.m.