Triple
T14074658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People’s Grocery (historical) |
E338699
|
entity |
| Predicate | workedOnIssue |
P2453
|
FINISHED |
| Object | food insecurity |
—
|
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: food insecurity | Statement: [People’s Grocery (historical), workedOnIssue, food insecurity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedOnIssue Context triple: [People’s Grocery (historical), workedOnIssue, food insecurity]
-
A.
worksOnIssue
chosen
Indicates that an entity (typically a person or team) is actively engaged in addressing, resolving, or contributing work toward a specific issue.
-
B.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
C.
workedUnder
Indicates that one entity was hierarchically subordinate to and performed work under the supervision or authority of another entity.
-
D.
includedWorkOn
Indicates that one entity contains, features, or incorporates another entity as a work or component within it.
-
E.
hasWorkDedicatedTo
Indicates that one entity has a work (such as a book, artwork, or composition) that is formally dedicated to another entity.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5bc49881909012b66fa451f495 |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.