Triple
T27750745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WS-Discovery |
E702105
|
entity |
| Predicate | discoveryScope |
P170979
|
FINISHED |
| Object | multicast group |
—
|
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: multicast group | Statement: [WS-Discovery, discoveryScope, multicast group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryScope Context triple: [WS-Discovery, discoveryScope, multicast group]
-
A.
discoveryTarget
Indicates that one entity is the object, subject, or focus that another entity discovers or aims to discover.
-
B.
acquisitionScope
Indicates the extent, boundaries, or coverage of what is obtained or brought under control through an acquisition.
-
C.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
D.
discoverySurvey
Indicates that an entity conducts or is associated with an initial exploratory survey or assessment to gather foundational information.
-
E.
schemeDiscovery
Indicates that an entity discovers, identifies, or uncovers a particular scheme, plan, or structured method.
- F. None of above. chosen
Provenance (4 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_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 27, 2026, 4:20 p.m.