Triple
T19385074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBB |
E484911
|
entity |
| Predicate | linkedToCovenantTightness |
P136252
|
FINISHED |
| Object | may require somewhat tighter covenants than higher ratings |
—
|
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: may require somewhat tighter covenants than higher ratings | Statement: [BBB, linkedToCovenantTightness, may require somewhat tighter covenants than higher ratings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToCovenantTightness Context triple: [BBB, linkedToCovenantTightness, may require somewhat tighter covenants than higher ratings]
-
A.
relatedCovenant
Indicates a relationship in which one covenant is connected to, associated with, or derived from another covenant.
-
B.
covenantAssociation
Indicates a formal, binding relationship or agreement that associates entities under shared obligations, promises, or terms.
-
C.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
D.
covenantScope
Indicates the extent or boundaries of obligations, promises, or terms covered by a covenant or formal agreement between parties.
-
E.
covenantStatus
Indicates the current state or condition of a covenant or binding agreement between parties.
- F. None of above. chosen
Provenance (4 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b3ffa548190a060d6e94562a5d2 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e50213571881909cd7543a43b51986 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:35 p.m.