Triple
T17559431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fast Application Notification |
E427660
|
entity |
| Predicate | typicalClients |
P82339
|
FINISHED |
| Object | JDBC applications |
—
|
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: JDBC applications | Statement: [Fast Application Notification, typicalClients, JDBC applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClients Context triple: [Fast Application Notification, typicalClients, JDBC applications]
-
A.
intendedClients
chosen
Indicates the entities that a product, service, or action is specifically designed or targeted to serve as clients.
-
B.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
C.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
D.
portraysNotableClient
Indicates that an entity depicts or represents a client who is considered notable or distinguished.
-
E.
typicalProvider
Indicates that one entity commonly or characteristically serves as a provider of goods, services, or resources to another entity.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562573e48190a19f30fe915a5455 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.