Triple
T24515026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holycross |
E606340
|
entity |
| Predicate | hasProtectedStructure |
P156576
|
FINISHED |
| Object | Holycross Abbey |
—
|
NE NERFINISHED |
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: Holycross Abbey | Statement: [Holycross, hasProtectedStructure, Holycross Abbey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectedStructure Context triple: [Holycross, hasProtectedStructure, Holycross Abbey]
-
A.
isProtectedFrom
Indicates that one entity is safeguarded or shielded against harm, damage, or adverse effects caused by another entity or factor.
-
B.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
C.
hasStrictProtection
Indicates that an entity is subject to strong, enforceable safeguards or restrictions that tightly limit how it can be accessed, used, or altered.
-
D.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
E.
hasHiddenStructure
Indicates that an entity possesses an internal or underlying structure that is not directly visible or apparent.
- F. None of above. chosen
Provenance (4 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a9d795288190916368e3cec1f666 |
completed | April 30, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:24 a.m.