Triple
T29006611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Phat Diem |
E736452
|
entity |
| Predicate | hasCathedralComplexFeature |
P29783
|
FINISHED |
| Object | stone churches |
—
|
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: stone churches | Statement: [Diocese of Phat Diem, hasCathedralComplexFeature, stone churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCathedralComplexFeature Context triple: [Diocese of Phat Diem, hasCathedralComplexFeature, stone churches]
-
A.
hasCathedralType
Indicates that an entity is associated with, classified by, or designated as having a specific type or category of cathedral.
-
B.
containsCathedral
Indicates that one entity includes or has within its boundaries a cathedral associated with it.
-
C.
cathedralFeature
chosen
Indicates that one entity is a distinctive architectural or structural feature of a cathedral.
-
D.
hasCathedralTown
Indicates that a given town is recognized as having a cathedral, typically serving as the seat of a bishop or central church authority.
-
E.
hasCathedralStyle
Indicates that something possesses or is characterized by a particular architectural style associated with a cathedral.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 28, 2026, 9:38 a.m.