Triple
T34787398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Rogativa procession of 1797 |
E1002847
|
entity |
| Predicate | tookPlaceWithin |
P84795
|
FINISHED |
| Object | walled city of San Juan |
—
|
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: walled city of San Juan | Statement: [La Rogativa procession of 1797, tookPlaceWithin, walled city of San Juan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPlaceWithin Context triple: [La Rogativa procession of 1797, tookPlaceWithin, walled city of San Juan]
-
A.
tookPlaceAtLocation
Indicates that an event or action occurred at a specific location.
-
B.
tookPlaceInAdministrativeEntity
Indicates that an event or occurrence happened within the jurisdiction or boundaries of a specific administrative entity.
-
C.
takesPlace
Indicates that an event or action occurs or is situated at a particular time, place, or context.
-
D.
takesPlaceInRegion
chosen
Indicates that an event or occurrence happens within the boundaries of a specified geographic or administrative region.
-
E.
tookPlaceFrom
Indicates that an event or occurrence started or was ongoing beginning at a specified time or 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.