Triple
T29503752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proxy-Authorization |
E748453
|
entity |
| Predicate | processingBy |
P82893
|
FINISHED |
| Object | intermediate proxy server |
—
|
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: intermediate proxy server | Statement: [Proxy-Authorization, processingBy, intermediate proxy server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processingBy Context triple: [Proxy-Authorization, processingBy, intermediate proxy server]
-
A.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
B.
processingOrder
Indicates the sequence or priority in which items, tasks, or requests are to be processed or handled.
-
C.
processedTo
Indicates that one entity is transformed or converted into another entity through some processing operation.
-
D.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
E.
requiresProcessingBy
chosen
Indicates that one entity must undergo handling, treatment, or transformation performed by another entity before a condition is met or a process can continue.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 4:26 p.m.