Triple
T21989503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UDDI |
E543045
|
entity |
| Predicate | supportsDiscoveryBy |
P41968
|
FINISHED |
| Object | Business name |
—
|
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: Business name | Statement: [UDDI, supportsDiscoveryBy, Business name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDiscoveryBy Context triple: [UDDI, supportsDiscoveryBy, Business name]
-
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.
supportsFinding
chosen
Indicates that one entity provides the capability or functionality needed to perform, enable, or carry out a particular finding operation on another entity or resource.
-
D.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
-
E.
hasDiscoveryType
Indicates the specific manner, method, or category by which something was discovered.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270cb67c81909a3aa2dc61c1894f |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:05 p.m.