Triple
T8247620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Build Service |
E192886
|
entity |
| Predicate | developer |
P73
|
FINISHED |
| Object | SUSE |
E192884
|
NE 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: SUSE | Statement: [Build Service, developer, SUSE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SUSE Context triple: [Build Service, developer, SUSE]
-
A.
SUSE
chosen
SUSE is a German-based open-source software company best known for its enterprise Linux distributions and related infrastructure solutions.
-
B.
openSUSE
openSUSE is a community-driven Linux distribution known for its stability, powerful administration tools like YaST, and close association with SUSE Linux Enterprise.
-
C.
Red Hat
Red Hat is a leading American open-source software company best known for its enterprise Linux distribution and related cloud and middleware solutions.
-
D.
Perseus Distribution
Perseus Distribution is a book distribution company that provides sales, marketing, and logistical services to independent publishers and imprints.
-
E.
Red Hat Enterprise Linux
Red Hat Enterprise Linux is a commercially supported, enterprise-grade Linux distribution widely used for servers, cloud deployments, and mission-critical applications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7875318c819095f971ba513c54fd |
completed | March 31, 2026, 7:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce4d7ff2a88190964a272647245bdc |
completed | April 2, 2026, 11:05 a.m. |
Created at: March 30, 2026, 5:48 p.m.