Triple
T2720610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | São Paulo Cathedral |
E60070
|
entity |
| Predicate | cryptLocation |
P41852
|
FINISHED |
| Object | under the main altar |
—
|
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: under the main altar | Statement: [São Paulo Cathedral, cryptLocation, under the main altar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cryptLocation Context triple: [São Paulo Cathedral, cryptLocation, under the main altar]
-
A.
securityLocation
Indicates the place or area where security-related activities, measures, or responsibilities are situated or applied.
-
B.
mountingLocation
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
C.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
D.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
E.
cabLocation
Indicates the current geographic position of a cab in space (e.g., on a map or within a defined area).
- F. None of above. chosen
Provenance (4 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdab06d388190acf690787fe58ab5 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd949c120819099a9d56eb71a0339 |
completed | March 7, 2026, 7:52 a.m. |
Created at: March 6, 2026, 9:55 p.m.