Triple
T27750726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WS-Discovery |
E702105
|
entity |
| Predicate | supportsDiscoveryMode |
P99857
|
FINISHED |
| Object | ad-hoc |
—
|
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: ad-hoc | Statement: [WS-Discovery, supportsDiscoveryMode, ad-hoc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDiscoveryMode Context triple: [WS-Discovery, supportsDiscoveryMode, ad-hoc]
-
A.
supportedDiscoveryOf
Indicates that one entity aided, enabled, or contributed to another entity’s act of discovering something.
-
B.
hasDiscoveryFeature
Indicates that an entity includes or supports a capability for discovering, finding, or surfacing other relevant entities, items, or information.
-
C.
supportedMode
chosen
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
D.
hasDiscoveryStatus
Indicates the current state or phase of discovery or identification associated with an entity.
-
E.
hasDiscoveryFacility
Indicates that an entity has, is associated with, or is served by a facility where discoveries (such as scientific, medical, or technological findings) are made or were made.
- 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_69fffc783b648190bcd7df017514d206 |
completed | May 10, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69fffc03fa24819099e12413dc6e0afd |
completed | May 10, 2026, 3:31 a.m. |
Created at: April 27, 2026, 4:20 p.m.