Triple
T30422107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCN |
E773926
|
entity |
| Predicate | supportsComponentVideo |
P145480
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [GCN, supportsComponentVideo, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsComponentVideo Context triple: [GCN, supportsComponentVideo, yes]
-
A.
supportsVideoPlayback
Indicates that an entity is capable of playing or rendering video content.
-
B.
hasIntegratedVideo
Indicates that an entity includes built-in video capabilities as an integral part of itself, rather than relying on an external video component.
-
C.
hasCompositeVideoOutput
chosen
Indicates that a device provides a composite video output connection for transmitting standard-definition analog video signals.
-
D.
supportsMinimumVideoConfiguration
Indicates that an entity is capable of meeting or exceeding the defined minimum requirements for a given video configuration.
-
E.
supportsVerticalVideo
Indicates that one entity provides compatibility with or proper handling of vertical (portrait-oriented) video content for another 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:06 p.m.