Triple
T33636456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cullen Post |
E861709
|
entity |
| Predicate | organizationMission |
P183523
|
FINISHED |
| Object | overturning wrongful convictions |
—
|
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: overturning wrongful convictions | Statement: [Cullen Post, organizationMission, overturning wrongful convictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationMission Context triple: [Cullen Post, organizationMission, overturning wrongful convictions]
-
A.
organizationMissionSupported
Indicates that an organization’s mission is actively backed, promoted, or furthered by another entity or activity.
-
B.
organizationGoal
chosen
Indicates that an organization has a specific goal, objective, or intended outcome it aims to achieve.
-
C.
describesMissionOf
Indicates that one entity specifies, explains, or defines the mission or purpose of another entity.
-
D.
missionFocus
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
-
E.
establishedMissionFor
Indicates that an entity formally created or set up a specific mission, assigning it purpose or objectives.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 1:42 a.m.