Triple
T8962544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marmashen Monastery |
E214042
|
entity |
| Predicate | mainChurchCompletion |
P47627
|
FINISHED |
| Object | circa 1029 |
—
|
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: circa 1029 | Statement: [Marmashen Monastery, mainChurchCompletion, circa 1029]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainChurchCompletion Context triple: [Marmashen Monastery, mainChurchCompletion, circa 1029]
-
A.
mainChurchBuilt
Indicates that the primary church associated with an entity was constructed or established at a particular time or by a particular agent.
-
B.
churchConstructionCompleted
chosen
Indicates that the process of building or constructing a church has been finished.
-
C.
hasCathedralCompletedIn
Indicates that a cathedral associated with an entity was completed in a specified year or time period.
-
D.
cathedralStatus
Indicates that an entity holds the official status or designation of a cathedral within a religious or ecclesiastical context.
-
E.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6749e5008190a01f42a2e772dd54 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:01 p.m.