Triple
T18616806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Educational System |
E455042
|
entity |
| Predicate | operatesProgramsIn |
P41907
|
FINISHED |
| Object | multiple languages |
—
|
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: multiple languages | Statement: [Church Educational System, operatesProgramsIn, multiple languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesProgramsIn Context triple: [Church Educational System, operatesProgramsIn, multiple languages]
-
A.
worksOnProgram
Indicates that an entity is actively involved in contributing effort or performing tasks on a particular program.
-
B.
programOperation
Indicates an operation or action performed by, within, or upon a program in a computational or procedural context.
-
C.
operateIn
chosen
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
D.
userProgram
Indicates that a user is associated with, uses, or is responsible for a particular program.
-
E.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d05da9c8190b8f4ef3a7a6deb05 |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.