Triple
T27845641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustine Commission |
E703812
|
entity |
| Predicate | evaluatedProgram |
P163733
|
FINISHED |
| Object | Constellation program |
—
|
NE NERFINISHED |
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: Constellation program | Statement: [Augustine Commission, evaluatedProgram, Constellation program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluatedProgram Context triple: [Augustine Commission, evaluatedProgram, Constellation program]
-
A.
producedProgram
Indicates that one entity created or produced a specific program (such as a TV show, software, or other structured content).
-
B.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
C.
implementsProgram
Indicates that an entity carries out, executes, or puts into effect a specified program or plan.
-
D.
servedProgram
Indicates that an entity has provided, delivered, or made available a particular program to another party or context.
-
E.
intendedProgram
Indicates the academic or training program that an entity plans or expects to pursue, rather than one they are currently enrolled in or have completed.
- F. None of above. chosen
Provenance (4 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 6:07 p.m.