Triple
T13889111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Civil Service |
E333922
|
entity |
| Predicate | implementationRole |
P56870
|
FINISHED |
| Object | executing welfare schemes at local level |
—
|
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: executing welfare schemes at local level | Statement: [State Civil Service, implementationRole, executing welfare schemes at local level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementationRole Context triple: [State Civil Service, implementationRole, executing welfare schemes at local level]
-
A.
roleInOperation
chosen
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
B.
technologyRole
Indicates the functional role or purpose that a technology plays within a system, process, or context.
-
C.
codeRole
Indicates a relationship where an entity serves a specific role or function within a piece of code or software system.
-
D.
roleInSpecification
Indicates that an entity participates in a specification with a particular role or function within that specification.
-
E.
effectiveRole
Indicates the functional role or capacity an entity actually performs or holds in a given context, regardless of its formal or nominal designation.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a3a24881908d81d634622fbbcc |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.