Triple
T20477618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajendra Singh |
E502359
|
entity |
| Predicate | roleInRSS |
P6124
|
FINISHED |
| Object | strengthening organizational discipline |
—
|
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: strengthening organizational discipline | Statement: [Rajendra Singh, roleInRSS, strengthening organizational discipline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRSS Context triple: [Rajendra Singh, roleInRSS, strengthening organizational discipline]
-
A.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
B.
roleInMetadata
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
-
C.
roleInVox
Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
-
D.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
E.
roleInvolves
chosen
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69966b9748190a5296d8ab03c07a1 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.