Triple
T29934242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Nomad |
E760311
|
entity |
| Predicate | tvPlaySupport |
P168275
|
FINISHED |
| Object | can be connected to a television for play |
—
|
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: can be connected to a television for play | Statement: [Sega Nomad, tvPlaySupport, can be connected to a television for play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tvPlaySupport Context triple: [Sega Nomad, tvPlaySupport, can be connected to a television for play]
-
A.
televisionPlatform
Indicates that one entity serves as the television platform (e.g., service, system, or distribution channel) through which the other entity’s TV content is delivered or accessed.
-
B.
playsOn
Indicates that one entity participates or performs on a particular team, platform, or medium.
-
C.
streamingService
Indicates that one entity provides or delivers media content over the internet to another entity in real time or on demand.
-
D.
tvShareUS
Indicates the proportion of television viewership or audience share that occurs within the United States.
-
E.
supportsRemotePlay
Indicates that one entity enables or is compatible with remote play functionality for another entity.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677d346e4819089c1c7231d9df64e |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:19 p.m.