Triple
T9183387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Genesis Model 3 |
E220389
|
entity |
| Predicate | hasVideoOutput |
P83205
|
FINISHED |
| Object | composite video |
—
|
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: composite video | Statement: [Sega Genesis Model 3, hasVideoOutput, composite video]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVideoOutput Context triple: [Sega Genesis Model 3, hasVideoOutput, composite video]
-
A.
videoOutput
Indicates that one entity produces or provides video signals or content as output to another entity or medium.
-
B.
hasVideoRecordingAvailableOn
Indicates that a video recording of something is accessible or hosted on a specified platform, service, or medium.
-
C.
hasVideoRecording
Indicates that there exists an associated video recording capturing or documenting the referenced entity or event.
-
D.
hasVideoBoard
Indicates that an entity is equipped with or includes a video board (graphics/display hardware component).
-
E.
videoOutputConnector
chosen
Indicates a relationship where a device or component provides a connector used to output video signals to an external display or receiver.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31734908190b8ebe3b57849ca5f |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.