Triple
T14705214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End Poverty in California |
E345409
|
entity |
| Predicate | notableSupportBase |
P98916
|
FINISHED |
| Object | unemployed workers |
—
|
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: unemployed workers | Statement: [End Poverty in California, notableSupportBase, unemployed workers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSupportBase Context triple: [End Poverty in California, notableSupportBase, unemployed workers]
-
A.
notableSupport
Indicates that one entity provides significant, recognized backing, endorsement, or assistance to another.
-
B.
notableSupportBaseCharacteristic
chosen
Indicates that a subject’s base of support is distinguished by a particular notable characteristic or quality.
-
C.
notableBase
Indicates that a particular location serves as a significant or distinguished base or headquarters for an entity.
-
D.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
E.
mainSupportBase
Indicates that one entity serves as the primary structural or functional support base for 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb6086c608190a66c64e23a3e002f |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.