Triple
T24840554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretariat of Social Development of Mexico |
E621601
|
entity |
| Predicate | operatedProgram |
P146254
|
FINISHED |
| Object | Prospera |
—
|
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: Prospera | Statement: [Secretariat of Social Development of Mexico, operatedProgram, Prospera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedProgram Context triple: [Secretariat of Social Development of Mexico, operatedProgram, Prospera]
-
A.
programOperation
Indicates an operation or action performed by, within, or upon a program in a computational or procedural context.
-
B.
servedProgram
chosen
Indicates that an entity has provided, delivered, or made available a particular program to another party or context.
-
C.
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.
-
D.
userProgram
Indicates that a user is associated with, uses, or is responsible for a particular program.
-
E.
programOn
Indicates that a program is scheduled to be broadcast or presented on a particular channel, station, platform, or device.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 18, 2026, 5:18 a.m.