Triple
T29892363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | charkha |
E759186
|
entity |
| Predicate | advocatedAs |
P33
|
FINISHED |
| Object | tool for economic upliftment of villages |
—
|
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: tool for economic upliftment of villages | Statement: [charkha, advocatedAs, tool for economic upliftment of villages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advocatedAs Context triple: [charkha, advocatedAs, tool for economic upliftment of villages]
-
A.
advocatesIn
Indicates that an entity actively supports, promotes, or argues in favor of something within a particular context, domain, or setting.
-
B.
advocates
chosen
Indicates that one entity publicly supports, recommends, or argues in favor of another entity or its interests.
-
C.
advocatesAgainst
Indicates that one entity actively opposes, argues against, or campaigns to prevent or stop another entity, action, or idea.
-
D.
stoodFor
Indicates that one entity represented, supported, or defended another entity, cause, or principle, often in a public or symbolic way.
-
E.
advisorOf
Indicates that one entity serves as an advisor, providing guidance or counsel, 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67728a5208190a43626fb4f5669c7 |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:03 p.m.