Triple
T34787390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Rogativa procession of 1797 |
E1002847
|
entity |
| Predicate | hasMonumentLocation |
P198121
|
FINISHED |
| Object | near San Juan city walls |
—
|
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: near San Juan city walls | Statement: [La Rogativa procession of 1797, hasMonumentLocation, near San Juan city walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonumentLocation Context triple: [La Rogativa procession of 1797, hasMonumentLocation, near San Juan city walls]
-
A.
hasMonumentAt
chosen
Indicates that a monument is located at or associated with a specific place or site.
-
B.
hasMarkerOrMonument
Indicates that something possesses or is associated with a physical marker or monument commemorating it.
-
C.
monumentsLocation
Indicates the geographical place where a monument is situated or located.
-
D.
hasPrimaryMonument
Indicates that an entity is associated with its main or most significant monument.
-
E.
hasScheduledMonument
Indicates that an entity is associated with, or contains, a site or structure officially designated as a scheduled monument.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 3, 2026, 3:59 p.m.