Triple
T36751970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisa |
E907936
|
entity |
| Predicate | supportsInterlaced |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInterlaced Context triple: [Lisa, supportsInterlaced, yes]
-
A.
supportsInterlacing
Indicates that one entity is capable of handling or enabling interlaced data or processing for another entity.
-
B.
supportsInterlacedVideo
chosen
Indicates that an entity is capable of handling, processing, or displaying interlaced video signals.
-
C.
supportsInterlacedCompositeArtifacts
Indicates that one entity provides compatibility with or functionality for handling interlaced composite artifacts associated with another entity.
-
D.
supportsNonInterlacedModes
Indicates that an entity is capable of handling or operating with non-interlaced (progressive) display modes.
-
E.
interlaced
Indicates that two or more things are intricately intertwined or alternated with each other in a closely connected pattern.
- F. None of above.
Provenance (1 batch)
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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.