Triple
T20085017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Trinity Brompton Church |
E500102
|
entity |
| Predicate | roleInAlphaCourse |
P116704
|
FINISHED |
| Object | birthplace of the Alpha course |
—
|
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: birthplace of the Alpha course | Statement: [Holy Trinity Brompton Church, roleInAlphaCourse, birthplace of the Alpha course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAlphaCourse Context triple: [Holy Trinity Brompton Church, roleInAlphaCourse, birthplace of the Alpha course]
-
A.
courseRole
chosen
Indicates the specific function or position an individual holds within a course, such as student, instructor, or assistant.
-
B.
roleInTrain
Indicates the specific function or position an entity holds within the context of a train (e.g., passenger, conductor, locomotive, or car type).
-
C.
roleInWorkshop
Indicates the specific function or position an entity holds within the context of a particular workshop.
-
D.
roleAtInstructure
Indicates that an entity holds a specific role or position within the organization Instructure.
-
E.
onCourse
Indicates that one entity is currently enrolled in, participating in, or following a particular course.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655ae9ec8190bde2f17452639de8 |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:41 p.m.