Triple
T36044530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gardar Cathedral |
E1042631
|
entity |
| Predicate | foundedAsEpiscopalSee |
P91840
|
FINISHED |
| Object | 12th century |
—
|
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: 12th century | Statement: [Gardar Cathedral, foundedAsEpiscopalSee, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsEpiscopalSee Context triple: [Gardar Cathedral, foundedAsEpiscopalSee, 12th century]
-
A.
dioceseErectedOn
Indicates the date or point in time when a diocese was formally established or created.
-
B.
episcopalSeeOf
Indicates that one entity serves as the episcopal see (the official seat or jurisdictional center) of a bishop or similar ecclesiastical authority for another entity.
-
C.
periodAsEpiscopalSeeStart
chosen
Indicates the point in time when a location begins its role or status as an episcopal see.
-
D.
dioceseEstablishedBy
Indicates that a diocese was founded, created, or formally instituted by a particular person or authority.
-
E.
majorArchepiscopalSee
Indicates that one entity serves as the principal episcopal jurisdiction (major archiepiscopal see) governing or presiding over the other within a particular church or rite.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:07 p.m.