Triple
T2940798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naples Cathedral |
E79380
|
entity |
| Predicate | hasPortal |
P44087
|
FINISHED |
| Object | main marble portal |
—
|
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: main marble portal | Statement: [Naples Cathedral, hasPortal, main marble portal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortal Context triple: [Naples Cathedral, hasPortal, main marble portal]
-
A.
hasPortico
Indicates that one entity (typically a building or structure) features a portico as part of its architectural design.
-
B.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
C.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
D.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
E.
isOfficialPortalFor
Indicates that one entity serves as the recognized, authoritative portal or entry point for accessing information or services related to another entity.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad986f38948190a636a826693a9d4f |
completed | March 8, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:56 p.m.