Triple
T28509162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | xHydra |
E721435
|
entity |
| Predicate | legalNotice |
P57992
|
FINISHED |
| Object | intended for authorized security testing only |
—
|
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: intended for authorized security testing only | Statement: [xHydra, legalNotice, intended for authorized security testing only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalNotice Context triple: [xHydra, legalNotice, intended for authorized security testing only]
-
A.
lawStatement
Indicates that an entity expresses, codifies, or articulates a legal rule, principle, or requirement.
-
B.
legalLicenseIn
Indicates that an entity holds a valid legal license or authorization to operate, practice, or conduct a specified activity within a particular jurisdiction or region.
-
C.
legalDetail
Indicates that there is specific legal information, conditions, or attributes associated with the related entity or relationship.
-
D.
legalContent
Indicates that the associated material complies with applicable laws and regulations and is permitted for use, distribution, or display.
-
E.
requiresLicenseNotice
chosen
Indicates that performing the action or using the resource is contingent on providing or displaying a required license notice.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 28, 2026, 3:11 a.m.