Triple
T31311250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic culture |
E798466
|
entity |
| Predicate | featuresArchitecture |
P81514
|
FINISHED |
| Object | Coptic church |
—
|
NE NERFINISHED |
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: Coptic church | Statement: [Coptic culture, featuresArchitecture, Coptic church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresArchitecture Context triple: [Coptic culture, featuresArchitecture, Coptic church]
-
A.
featuresBuilding
Indicates that one entity includes or incorporates a building as a notable component or characteristic.
-
B.
architectFeatured
Indicates that an architect is prominently highlighted or showcased in relation to a particular work, project, or context.
-
C.
featuresStructure
chosen
Indicates that one entity possesses, exhibits, or incorporates a particular structure as a notable characteristic or component.
-
D.
architecturalFocus
Indicates that something is the primary subject, theme, or area of emphasis within the domain of architecture.
-
E.
featuresDecor
Indicates that one entity includes or showcases the decor elements provided or defined by another 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00717f539c8190b70dd0e72c6f7d24 |
completed | May 10, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a00710278fc81908889afdcf459ff01 |
completed | May 10, 2026, 11:50 a.m. |
Created at: April 29, 2026, 9:15 p.m.