Triple
T8067835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgetown Preparatory School |
E188289
|
entity |
| Predicate | hasReligiousOrderStaff |
P9815
|
FINISHED |
| Object | Jesuit priests |
—
|
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: Jesuit priests | Statement: [Georgetown Preparatory School, hasReligiousOrderStaff, Jesuit priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousOrderStaff Context triple: [Georgetown Preparatory School, hasReligiousOrderStaff, Jesuit priests]
-
A.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
-
B.
religiousOrderSupported
Indicates that one entity provides support—such as resources, endorsement, or maintenance—to a particular religious order.
-
C.
hasClergy
chosen
Indicates that an organization or institution possesses or is served by members of the clergy.
-
D.
religiousOrderAssociation
Indicates that an entity is formally connected to, affiliated with, or a member of a particular religious order.
-
E.
approvedReligiousOrder
Indicates that an authority has formally recognized and authorized a particular religious order.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ff8a4fc8190a97fc7111ca7ec4d |
completed | March 31, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:27 p.m.