Triple
T1892026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handycam |
E41893
|
entity |
| Predicate | supportsMedia |
P24486
|
FINISHED |
| Object | tape (in earlier models) |
—
|
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: tape (in earlier models) | Statement: [Handycam, supportsMedia, tape (in earlier models)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMedia Context triple: [Handycam, supportsMedia, tape (in earlier models)]
-
A.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
hasCommonMedia
Indicates that two entities share at least one media item (such as an image, video, or audio file) in common.
-
C.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportsView
Indicates that one entity provides the capability to display, render, or present another entity in a particular view or format.
-
E.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb145f96c8190a71bb9e442892e68 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.