Triple
T8436167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun 3/60 |
E199227
|
entity |
| Predicate | displayConnection |
P83359
|
FINISHED |
| Object | proprietary framebuffer connector |
—
|
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: proprietary framebuffer connector | Statement: [Sun 3/60, displayConnection, proprietary framebuffer connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displayConnection Context triple: [Sun 3/60, displayConnection, proprietary framebuffer connector]
-
A.
displayConfiguration
Indicates a relationship where one entity defines or presents the arrangement, layout, or settings used to visually display another entity.
-
B.
displayState
Indicates the current visual or presentation status of an item, such as whether and how it is shown, hidden, or rendered in a user interface or display context.
-
C.
displayMode
Indicates how content or information is visually presented or arranged to the user.
-
D.
displays
Indicates that one entity visually presents or shows another entity’s content or information.
-
E.
displayEnvironment
Indicates that an entity presents or renders a particular environment or environmental setting for viewing or interaction.
- F. None of above. chosen
Provenance (4 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:08 p.m.