Triple
T1378445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica of the Annunciation |
E29279
|
entity |
| Predicate | earlierStructureOnSite |
P11081
|
FINISHED |
| Object | Byzantine church |
—
|
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: Byzantine church | Statement: [Basilica of the Annunciation, earlierStructureOnSite, Byzantine church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierStructureOnSite Context triple: [Basilica of the Annunciation, earlierStructureOnSite, Byzantine church]
-
A.
previousStructure
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
B.
formerSiteOf
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
-
C.
originalBuildingConstructed
Indicates that a particular building was initially constructed in its original form or configuration.
-
D.
successorBuildingOnSite
chosen
Indicates that one building directly replaces another on the same physical site or location.
-
E.
constructionSite
Indicates that an entity is a location or area where construction work is actively taking place or is planned to occur.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c3173548819082aec7c1af9c577c |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befcabdc8190a9f05d002603f81c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.