Triple
T9497104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WRQ |
E229035
|
entity |
| Predicate | commonlyRestrictedBy |
P30858
|
FINISHED |
| Object | TFTP server access control |
—
|
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: TFTP server access control | Statement: [WRQ, commonlyRestrictedBy, TFTP server access control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyRestrictedBy Context triple: [WRQ, commonlyRestrictedBy, TFTP server access control]
-
A.
notableRestriction
Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
-
B.
restrictedFromUseFor
chosen
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
-
C.
notRestrictedBy
Indicates that something is free from limitations, constraints, or prohibitions imposed by another entity or condition.
-
D.
demographicRestriction
Indicates that participation, access, or applicability is limited or conditioned based on specific demographic characteristics (such as age, gender, ethnicity, or similar attributes).
-
E.
hasSemanticRestriction
Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95ecf4148190aa8f4733980166ae |
completed | April 1, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.