Triple
T1719043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PowerShell |
E37350
|
entity |
| Predicate | supportsInteractiveUse |
P27769
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [PowerShell, supportsInteractiveUse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInteractiveUse Context triple: [PowerShell, supportsInteractiveUse, true]
-
A.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
B.
hasInteractiveActivity
chosen
Indicates that an entity includes or is associated with an activity that requires active user participation or engagement.
-
C.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
D.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
-
E.
supportsUnregisteredUse
Indicates that an entity allows or enables the use of something without requiring prior registration or formal enrollment.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.