Triple
T27750746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WS-Discovery |
E702105
|
entity |
| Predicate | supportsProxyRole |
P10797
|
FINISHED |
| Object | discovery proxy |
—
|
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: discovery proxy | Statement: [WS-Discovery, supportsProxyRole, discovery proxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProxyRole Context triple: [WS-Discovery, supportsProxyRole, discovery proxy]
-
A.
supportsRole
chosen
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
B.
supportsRoleSwap
Indicates that one entity enables or allows the interchange of roles or responsibilities with another entity.
-
C.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
D.
supportsPrivilege
Indicates that one entity enables, upholds, or grants a particular privilege or special right to another entity.
-
E.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: April 27, 2026, 4:20 p.m.