Triple
T37511780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infiltration |
E932533
|
entity |
| Predicate | focusesOnAbility |
P160715
|
FINISHED |
| Object | hacking |
—
|
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: hacking | Statement: [Infiltration, focusesOnAbility, hacking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnAbility Context triple: [Infiltration, focusesOnAbility, hacking]
-
A.
emphasizesAbility
chosen
Indicates that one entity highlights, stresses, or draws special attention to the capability or skill of another entity.
-
B.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
sonAbility
Indicates that a son possesses or demonstrates a particular ability or capability in relation to another entity.
-
D.
focusTrait
Indicates that one entity is characterized by, or primarily associated with, a particular trait or attribute of another entity.
-
E.
believedToHaveAbility
Indicates that one entity is thought or assumed to possess a particular capability or power, without asserting that the ability is actually verified.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:17 p.m.