Triple
T4836483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisbon Cathedral |
E108070
|
entity |
| Predicate | mainPortalStyle |
P51375
|
FINISHED |
| Object | Romanesque |
—
|
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: Romanesque | Statement: [Lisbon Cathedral, mainPortalStyle, Romanesque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPortalStyle Context triple: [Lisbon Cathedral, mainPortalStyle, Romanesque]
-
A.
primaryBodyStyle
Indicates the main or predominant body configuration or structural form associated with an entity.
-
B.
primaryStyle
chosen
Indicates the main or predominant style associated with an entity, distinguishing it from other secondary or supporting styles.
-
C.
majorStyle
Indicates the primary artistic, aesthetic, or methodological style that characterizes or dominates something in relation to others.
-
D.
isOfficialPortalFor
Indicates that one entity serves as the recognized, authoritative portal or entry point for accessing information or services related to another entity.
-
E.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.