Triple
T14538971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SystemTap |
E341121
|
entity |
| Predicate | supportsDwarfBasedProbing |
P102483
|
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: [SystemTap, supportsDwarfBasedProbing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDwarfBasedProbing Context triple: [SystemTap, supportsDwarfBasedProbing, true]
-
A.
supportsDynamicInstrumentation
Indicates that an entity is capable of being instrumented or monitored at runtime without requiring recompilation or restart.
-
B.
supportsPositionIndependentCode
Indicates that one entity (such as a tool, platform, or environment) is capable of correctly handling or executing position-independent code generated by another.
-
C.
supportsBranchPrediction
Indicates that one entity provides functionality or mechanisms that enable or enhance branch prediction for another entity.
-
D.
hasDiscoveryFeature
Indicates that an entity includes or supports a capability for discovering, finding, or surfacing other relevant entities, items, or information.
-
E.
supportsDebugFormats
chosen
Indicates that one entity provides or is compatible with debugging data or formats used by another entity.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1bb90008190947ac0961393446d |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.