Triple
T19585621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mod_proxy |
E490098
|
entity |
| Predicate | controlledByDirective |
P42339
|
FINISHED |
| Object | ProxyRequests |
—
|
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: ProxyRequests | Statement: [mod_proxy, controlledByDirective, ProxyRequests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByDirective Context triple: [mod_proxy, controlledByDirective, ProxyRequests]
-
A.
controlledIn
Indicates that one entity exercised control, authority, or governance over another entity within a specific context or domain.
-
B.
controlledFor
Indicates that the influence or effect of a specified factor has been accounted for or neutralized when assessing the relationship between other variables or entities.
-
C.
usesDirective
Indicates that one entity applies, references, or relies on a specific directive issued or defined by another entity.
-
D.
effectControlledBy
Indicates that the occurrence, magnitude, or outcome of one effect is regulated, determined, or constrained by another specified factor or agent.
-
E.
hasDirective
chosen
Indicates that one entity issues, contains, or is governed by a specific directive or instruction associated with 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e640513134819082cf233fa3dcc911 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.