Triple
T2932591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FCNM |
E78987
|
entity |
| Predicate | typeOfObligations |
P445
|
FINISHED |
| Object | programmatic obligations |
—
|
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: programmatic obligations | Statement: [FCNM, typeOfObligations, programmatic obligations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfObligations Context triple: [FCNM, typeOfObligations, programmatic obligations]
-
A.
obligationType
chosen
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
-
B.
obligationCondition
Indicates that one situation or state serves as the condition under which an obligation for an entity becomes active or must be fulfilled.
-
C.
obligation
Indicates that one entity is bound or required to perform a duty, action, or fulfill a condition toward another entity or according to a rule or agreement.
-
D.
typeOfRequirement
Indicates that one requirement is classified as a specific kind or category of another, more general requirement.
-
E.
obligorText
Indicates that one entity is described as the party bearing the obligation or debt toward another entity, typically in a contractual or financial context.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983a4ae08190aa1aeb2747abd1a1 |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.