Triple
T641973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old St. Peter's Basilica |
E16757
|
entity |
| Predicate | apseLocation |
P17655
|
FINISHED |
| Object | west end |
—
|
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: west end | Statement: [Old St. Peter's Basilica, apseLocation, west end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apseLocation Context triple: [Old St. Peter's Basilica, apseLocation, west end]
-
A.
treatmentLocation
Indicates the place or facility where a treatment or medical intervention is administered to an entity.
-
B.
apologyLocation
Indicates the place or setting where an apology is made or occurs.
-
C.
locatedOff
Indicates that one entity is situated away from, but in the vicinity of, another entity or reference point, rather than directly on or within it.
-
D.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
E.
dischargeLocation
Indicates the place or facility where an entity (such as a person, object, or substance) is released, sent, or discharged to after a prior state or process.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f02bc2c8190b8a92b2505768c19 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49df0de3c81909721eb391ec94031 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.