Triple
T27560861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.261 |
E695764
|
entity |
| Predicate | supportsErrorResilienceFeatures |
P203
|
FINISHED |
| Object | limited compared to later standards |
—
|
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: limited compared to later standards | Statement: [H.261, supportsErrorResilienceFeatures, limited compared to later standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsErrorResilienceFeatures Context triple: [H.261, supportsErrorResilienceFeatures, limited compared to later standards]
-
A.
supportsFailure
Indicates that one entity provides assistance, resources, or backing to another entity specifically in situations of error, malfunction, or unsuccessful outcomes.
-
B.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
C.
supportsExceptionProcessing
Indicates that one entity provides the capability or mechanism for another entity to handle or process exceptions.
-
D.
supportedMode
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
E.
supportsEP
Indicates that one entity provides assistance, resources, or endorsement to another entity’s emergency preparedness (EP) efforts or program.
- 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_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: April 27, 2026, 1:39 p.m.