Triple
T33203436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extended Display Identification Data |
E849963
|
entity |
| Predicate | hasExtensionStandard |
P153446
|
FINISHED |
| Object | E-EDID |
—
|
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: E-EDID | Statement: [Extended Display Identification Data, hasExtensionStandard, E-EDID]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExtensionStandard Context triple: [Extended Display Identification Data, hasExtensionStandard, E-EDID]
-
A.
hasExtensionBy
Indicates that one entity is extended, augmented, or further developed by another entity.
-
B.
isPopularStandardFor
Indicates that something is widely accepted and commonly used as the standard choice for a particular purpose or context.
-
C.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
D.
hasAssociatedStandard
chosen
Indicates that something is linked to or governed by a particular standard or set of standards.
-
E.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:30 a.m.