Triple
T28899720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Software Components Group |
E732920
|
entity |
| Predicate | productUseCase |
P31467
|
FINISHED |
| Object | real-time control |
—
|
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: real-time control | Statement: [Software Components Group, productUseCase, real-time control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productUseCase Context triple: [Software Components Group, productUseCase, real-time control]
-
A.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
B.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
-
C.
productsUsedIn
Indicates that certain products are utilized or applied within a particular process, context, or entity.
-
D.
productExample
Indicates that one entity serves as an illustrative or sample instance of a product associated with another entity.
-
E.
productDomain
chosen
Indicates the domain, field, or area of application to which a given product belongs or is relevant.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 28, 2026, 8:01 a.m.