Triple
T27731396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.AttributeUsageAttribute |
E697437
|
entity |
| Predicate | affectsRuntimeBehaviorDirectly |
P123985
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [System.AttributeUsageAttribute, affectsRuntimeBehaviorDirectly, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsRuntimeBehaviorDirectly Context triple: [System.AttributeUsageAttribute, affectsRuntimeBehaviorDirectly, false]
-
A.
affectsBehaviorOf
Indicates that one entity produces a change or influence on the behavior, actions, or conduct of another entity.
-
B.
isRuntimeEnforced
Indicates that a rule, constraint, or condition is actively checked and enforced during program execution rather than at compile time or design time.
-
C.
affectsProgram
Indicates that one entity produces an influence or change on a program, altering its behavior, state, or outcome.
-
D.
hasDirectEffect
chosen
Indicates that one entity produces an immediate and unmediated impact or change on another entity.
-
E.
areAffectedBy
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 3:11 p.m.