Triple
T21714408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Andrew’s School |
E535985
|
entity |
| Predicate | chapelTradition |
P145058
|
FINISHED |
| Object | Episcopal |
—
|
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: Episcopal | Statement: [St. Andrew’s School, chapelTradition, Episcopal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chapelTradition Context triple: [St. Andrew’s School, chapelTradition, Episcopal]
-
A.
establishedTradition
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
B.
chapelCity
Indicates that a chapel is located in, or associated with, a particular city.
-
C.
hasChapelStyle
Indicates that a chapel possesses or is characterized by a particular architectural or stylistic design.
-
D.
foundedByTradition
Indicates that something was established or created according to a longstanding custom, practice, or tradition rather than by a specific individual or formal institution.
-
E.
followsCouncilTradition
Indicates that an entity adheres to established customs, practices, or precedents set by a council.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb5369be88190bafc10863d4d1bd7 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:47 p.m.