Triple
T31338769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Layde |
E799246
|
entity |
| Predicate | hasRuinedChurch |
P32402
|
FINISHED |
| Object | medieval parish 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: medieval parish church | Statement: [Layde, hasRuinedChurch, medieval parish church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuinedChurch Context triple: [Layde, hasRuinedChurch, medieval parish church]
-
A.
hasNumberOfChurchRuins
Indicates the quantity of church ruins associated with a given entity.
-
B.
originalChurchDestroyed
Indicates that the initially established church building was demolished or ceased to exist, typically due to destruction rather than relocation or replacement.
-
C.
hasReconstructedChurch
Indicates that an entity has rebuilt or restored a church, typically after damage, destruction, or disuse.
-
D.
cathedralDamagedIn
Indicates that a cathedral has been harmed or impaired as a result of a specified event, action, or circumstance.
-
E.
hasRuin
chosen
Indicates that one entity possesses, contains, or is associated with a ruin or ruined structure.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 9:16 p.m.