Triple
T5412855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary |
E121052
|
entity |
| Predicate | coreResponsibility |
P636
|
FINISHED |
| Object | managing correspondence |
—
|
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: managing correspondence | Statement: [Secretary, coreResponsibility, managing correspondence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreResponsibility Context triple: [Secretary, coreResponsibility, managing correspondence]
-
A.
responsibleFor
chosen
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
B.
accountabilityTo
Indicates that one entity is responsible for explaining, justifying, or answering for its actions, decisions, or outcomes to another entity.
-
C.
securityResponsibilityModel
Indicates the framework or scheme that defines how security responsibilities are allocated and managed among involved parties.
-
D.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
E.
ethicalResponsibility
Indicates a relationship in which an entity is morally obligated to act, decide, or respond in a certain way toward another entity or situation.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bb3c0c81908711784bc865ff03 |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.