Triple
T16821228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Margaret Hall Chapel |
E408896
|
entity |
| Predicate | hasChapelCommunity |
P124975
|
FINISHED |
| Object | Lady Margaret Hall Chapel community |
—
|
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: Lady Margaret Hall Chapel community | Statement: [Lady Margaret Hall Chapel, hasChapelCommunity, Lady Margaret Hall Chapel community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChapelCommunity Context triple: [Lady Margaret Hall Chapel, hasChapelCommunity, Lady Margaret Hall Chapel community]
-
A.
hasChapelLocation
Indicates that one entity serves as the physical location or site where a chapel associated with another entity is situated.
-
B.
hasChapelNearby
Indicates that one entity is located close to or in the vicinity of a chapel.
-
C.
hasChapelUse
Indicates that something is used, designated, or functions as a chapel or for chapel-related purposes.
-
D.
hasChapelProgram
Indicates that an institution or organization offers or conducts a chapel program as part of its activities or services.
-
E.
hasChapelStatus
Indicates that an entity holds a designated status or classification specifically related to a chapel.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e6b59c8190ad562a80e71ce54c |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:23 a.m.