Triple
T26068390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanercost Priory |
E657470
|
entity |
| Predicate | partiallyUsedAs |
P95595
|
FINISHED |
| Object | 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: parish church | Statement: [Lanercost Priory, partiallyUsedAs, parish church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyUsedAs Context triple: [Lanercost Priory, partiallyUsedAs, parish church]
-
A.
partiallyReusedAs
chosen
Indicates that one entity is used again as part of another entity, but only to a limited or incomplete extent rather than in its entirety.
-
B.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
usedInPartOf
Indicates that something is utilized or plays a functional role within a specific component or subpart of a larger whole.
-
D.
partiallyReusable
Indicates that an entity can be reused to some extent but not fully or indefinitely, implying limited or partial reusability.
-
E.
partUsed
Indicates that one entity is a component or part that is utilized in the construction, operation, or composition of another 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 7:26 p.m.