Triple
T31498058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XAVC HS |
E803602
|
entity |
| Predicate | basedOnCodec |
P64032
|
FINISHED |
| Object | H.265 |
—
|
NE NERFINISHED |
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: H.265 | Statement: [XAVC HS, basedOnCodec, H.265]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnCodec Context triple: [XAVC HS, basedOnCodec, H.265]
-
A.
usesCodec
chosen
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
-
B.
relatedCodec
Indicates that one entity is associated with or corresponds to another through a shared or compatible codec used for encoding or decoding data.
-
C.
basedOnStrategyOf
Indicates that one entity’s strategy is derived from, influenced by, or constructed using the strategy of another entity.
-
D.
commonlyAssociatedCodec
Indicates that one item is typically linked or paired with a particular codec in common usage or practice.
-
E.
basedOnType
Indicates that one entity is derived, determined, or classified according to the type or category of 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: April 30, 2026, 9:42 p.m.