Triple
T13478683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarragona Cathedral |
E318312
|
entity |
| Predicate | mainPortalFaces |
P22904
|
FINISHED |
| Object | west |
—
|
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 | Statement: [Tarragona Cathedral, mainPortalFaces, west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPortalFaces Context triple: [Tarragona Cathedral, mainPortalFaces, west]
-
A.
mainFacadeFaces
Indicates that the primary front facade of a structure is oriented toward or directed at a particular side, direction, or reference point.
-
B.
mainPortalDate
Indicates the primary or official date associated with a portal’s main event, status, or activation.
-
C.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
-
D.
mainEntranceOn
chosen
Indicates that the primary entrance of one entity is located on or faces toward another entity, such as a particular side, street, or boundary.
-
E.
hasPortal
Indicates that one entity possesses or provides access to a portal connecting to another location or entity.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf266c508190930d30776c09ce35 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.