Triple
T36346259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norman culture |
E895072
|
entity |
| Predicate | producedMonument |
P25270
|
FINISHED |
| Object | Durham Cathedral |
—
|
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: Durham Cathedral | Statement: [Norman culture, producedMonument, Durham Cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedMonument Context triple: [Norman culture, producedMonument, Durham Cathedral]
-
A.
builtMonument
chosen
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
-
B.
monumentType
Indicates the specific kind or category of monument that an entity is classified as.
-
C.
otherMonuments
Indicates that there exists a relationship between an entity and additional monuments that are associated with or related to it in some relevant way.
-
D.
hasMonumentFunction
Indicates that something serves the role or purpose of a monument, such as commemorating, honoring, or symbolizing a person, event, or idea.
-
E.
mainMonumentDesigner
Indicates that one entity is the primary architect or designer responsible for the creation or design of a particular monument.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 3, 2026, 4:09 p.m.