Triple
T34518643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Redemption Party |
E886221
|
entity |
| Predicate | supportBaseClass |
P130103
|
FINISHED |
| Object | urban poor |
—
|
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: urban poor | Statement: [People's Redemption Party, supportBaseClass, urban poor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportBaseClass Context triple: [People's Redemption Party, supportBaseClass, urban poor]
-
A.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
-
B.
supportedClass
Indicates that one entity is a class or type that is recognized, handled, or operable within the capabilities or context provided by another entity.
-
C.
supportBaseIncludes
chosen
Indicates that a broader support base encompasses or contains a specified subset or component of that support.
-
D.
IndependentSupportBase
Indicates that one entity serves as a foundational, self-sufficient support structure for another, not relying on additional supports or connections.
-
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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.