Triple
T26492499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lescar |
E669194
|
entity |
| Predicate | Lescar Cathedral |
P9020
|
FINISHED |
| Object | Romanesque cathedral |
—
|
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 cathedral | Statement: [Lescar, Lescar Cathedral, Romanesque cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Lescar Cathedral Context triple: [Lescar, Lescar Cathedral, Romanesque cathedral]
-
A.
cathedralLocatedIn
Indicates that a cathedral is situated within or belongs to a specific geographic or administrative location.
-
B.
cathedralChurchOfCanterbury
Indicates that one entity serves as the cathedral church associated with the ecclesiastical jurisdiction or see of Canterbury.
-
C.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
-
D.
coCathedral
Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
-
E.
cathedral
chosen
Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613535c1c81908e8da8d785be0cb4 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:05 a.m.