Triple
T36366986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prejmer fortified church |
E895651
|
entity |
| Predicate | mainChurchConstructionCentury |
P75550
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Prejmer fortified church, mainChurchConstructionCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainChurchConstructionCentury Context triple: [Prejmer fortified church, mainChurchConstructionCentury, 13th century]
-
A.
cathedralMainConstructionCentury
Indicates the century during which the primary phase of a cathedral’s construction took place.
-
B.
mainChurchBuilt
Indicates that the primary church associated with an entity was constructed or established at a particular time or by a particular agent.
-
C.
parishChurchCentury
chosen
Indicates the century during which a given parish church was established, built, or primarily dates from.
-
D.
originalChurchBuilt
Indicates that a particular church building was initially constructed at a given time or by a specified agent, before any later reconstructions or modifications.
-
E.
cathedralConstructionStarted
Indicates that the process of constructing a cathedral has begun.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:10 p.m.