Triple
T1050049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rossmanith GmbH |
E22673
|
entity |
| Predicate | softwareTypeAssociated |
P1482
|
FINISHED |
| Object | remote-access software |
—
|
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: remote-access software | Statement: [Rossmanith GmbH, softwareTypeAssociated, remote-access software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareTypeAssociated Context triple: [Rossmanith GmbH, softwareTypeAssociated, remote-access software]
-
A.
usesSoftware
Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
-
B.
sapType
Indicates the specific category or classification of SAP-related type assigned to an entity within a system or data model.
-
C.
programUsed
Indicates that a particular program, software, or application was employed or utilized in performing an action or achieving a result.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
technologyType
chosen
Indicates the specific kind or category of technology associated with an entity or relationship.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8b2c6208190b6fdf3e93b1b1d04 |
completed | March 1, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69a4b7309cc481908ed839b0b8d75dbf |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.