Triple
T8246894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APT |
E192870
|
entity |
| Predicate | defaultFrontEndOn |
P33528
|
FINISHED |
| Object | many Debian-based distributions |
—
|
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: many Debian-based distributions | Statement: [APT, defaultFrontEndOn, many Debian-based distributions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultFrontEndOn Context triple: [APT, defaultFrontEndOn, many Debian-based distributions]
-
A.
hasFrontend
Indicates that one entity serves as the user-facing interface or presentation layer for another entity.
-
B.
defaultBrowserOn
Indicates that a particular browser is set as the default browser on a given device or system.
-
C.
defaultOn
chosen
Indicates that something is in an enabled or active state by default, without requiring explicit activation.
-
D.
usedOnFront
Indicates that something is applied, displayed, or positioned on the front side or front-facing part of another object or entity.
-
E.
operatedOnFront
Indicates that an action or operation was performed specifically on the front side or front-facing part of an 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb787414508190a08cf47d1545ce50 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.