Triple
T33351855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of Luján |
E853963
|
entity |
| Predicate | firstVenerationSite |
P5455
|
FINISHED |
| Object | Rosendo de Oramas’s ranch near Luján |
—
|
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: Rosendo de Oramas’s ranch near Luján | Statement: [Our Lady of Luján, firstVenerationSite, Rosendo de Oramas’s ranch near Luján]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstVenerationSite Context triple: [Our Lady of Luján, firstVenerationSite, Rosendo de Oramas’s ranch near Luján]
-
A.
veneratedAt
chosen
Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
-
B.
firstBurial
Indicates that an entity is the earliest or initial burial associated with a person, place, or burial context.
-
C.
isVotiveMonumentOf
Indicates that an object is a votive monument dedicated or offered in honor of a particular entity.
-
D.
firstRevelationPlace
Indicates the location where something (typically a text, message, or revelation) was first revealed or disclosed.
-
E.
veneratedOn
Indicates that an entity is honored, revered, or celebrated on a specific date or occasion.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:34 a.m.