Triple
T14031559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrytown Catholic High School |
E337601
|
entity |
| Predicate | servesReligion |
P2330
|
FINISHED |
| Object | Catholic 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: Catholic community | Statement: [Harrytown Catholic High School, servesReligion, Catholic community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesReligion Context triple: [Harrytown Catholic High School, servesReligion, Catholic community]
-
A.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
-
B.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
-
C.
religiousFunction
chosen
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
D.
religiousTarget
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
-
E.
majorReligionCanBe
Indicates that an entity can have a particular major religion as one of its possible primary religious affiliations.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fab17008190981f1808726fa11c |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.