Triple
T38656318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Cathedral of Jaro |
E939899
|
entity |
| Predicate | belfryLocated |
P88906
|
FINISHED |
| Object | across Jaro Plaza |
—
|
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: across Jaro Plaza | Statement: [Metropolitan Cathedral of Jaro, belfryLocated, across Jaro Plaza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belfryLocated Context triple: [Metropolitan Cathedral of Jaro, belfryLocated, across Jaro Plaza]
-
A.
belfryListedAs
Indicates that a belfry is officially recorded or registered under a particular listing or designation.
-
B.
hasBellTowerLocation
chosen
Indicates the specific location where a bell tower is situated or attached relative to another structure or place.
-
C.
hasBellFoundry
Indicates that an entity operates, owns, or is associated with a facility where bells are manufactured or cast.
-
D.
bellFoundry
Indicates that an entity operates as a foundry where bells are manufactured or cast.
-
E.
hasBellTower
Indicates that one entity (typically a building or structure) possesses or includes a bell tower as part of it.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.