Triple
T31664198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STBG Program |
E808080
|
entity |
| Predicate | allowsFlexibility |
P167053
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [STBG Program, allowsFlexibility, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsFlexibility Context triple: [STBG Program, allowsFlexibility, yes]
-
A.
flexibility
Indicates the degree to which an entity can adapt, bend, or change its behavior, structure, or response in relation to other entities or conditions.
-
B.
providesFlexibilityFor
chosen
Indicates that one entity offers options, adaptability, or freedom of choice to another entity in how something is done or used.
-
C.
hasFlexibilityClause
Indicates that an agreement or contract includes a clause allowing certain terms or conditions to be adjusted or modified under specified circumstances.
-
D.
positionFlexibility
Indicates the degree to which an entity’s role, location, or alignment can change or be adjusted relative to others or to a reference point.
-
E.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 30, 2026, 10:58 p.m.