Triple
T33193838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunday school teacher |
E849690
|
entity |
| Predicate | typicallyWorksAt |
P93741
|
FINISHED |
| Object | church |
—
|
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: church | Statement: [Sunday school teacher, typicallyWorksAt, church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyWorksAt Context triple: [Sunday school teacher, typicallyWorksAt, church]
-
A.
workAt
chosen
Indicates that an entity is employed by or performs work for a particular organization, company, or place.
-
B.
hasWorksIn
Indicates that one entity is employed by or performs their professional activities within the organization, location, or context represented by another entity.
-
C.
laterWorksAt
Indicates that an entity begins working at a place or organization at a time later than another referenced time or employment situation.
-
D.
worksNear
Indicates that one entity performs its work or duties in close physical proximity to another entity.
-
E.
worksInOrganizationType
Indicates that an entity is employed by or performs work within an organization of a specified type (e.g., company, nonprofit, government agency).
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:29 a.m.