Triple
T27560853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.261 |
E695764
|
entity |
| Predicate | usesGOPStructure |
P35482
|
FINISHED |
| Object | sequences of intra and inter pictures |
—
|
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: sequences of intra and inter pictures | Statement: [H.261, usesGOPStructure, sequences of intra and inter pictures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGOPStructure Context triple: [H.261, usesGOPStructure, sequences of intra and inter pictures]
-
A.
usedStructure
chosen
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
B.
hasStructureCode
Indicates that an entity is associated with a specific structural identifier or code that defines its organization or configuration.
-
C.
indicatesStructure
Indicates that one entity specifies, defines, or reveals the structural organization or arrangement of another entity.
-
D.
internalStructure
Indicates that one entity is a component, part, or substructure contained within the overall structure of another entity.
-
E.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62fb974e08190a01b9c243e9e8193 |
completed | May 2, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:39 p.m.