Triple
T10973697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VHS |
E259313
|
entity |
| Predicate | becameDominantStandard |
P56602
|
FINISHED |
| Object | late 1970s |
—
|
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: late 1970s | Statement: [VHS, becameDominantStandard, late 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameDominantStandard Context triple: [VHS, becameDominantStandard, late 1970s]
-
A.
becameStandardFor
Indicates that something was adopted and established as the usual or accepted norm for a particular purpose, context, or group.
-
B.
implementedAsStandardBy
Indicates that a standard is put into practice or realized through implementation by a specific entity (such as an organization, system, or component).
-
C.
wasGraduallyStandardizedIn
Indicates that something became standardized or uniform within a particular context through a gradual, step-by-step process over time.
-
D.
firstStandardApproved
Indicates that an entity is the earliest or initial standard that has received formal approval.
-
E.
becameStandardIn
chosen
Indicates that something was adopted and recognized as the standard within a particular context, domain, or time period.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7719c16648190ab5a87abb1c61990 |
completed | April 9, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:24 p.m.